This guide applies the PUDL menu-bar conventions to parkscomputing.com and yavchn.parkscomputing.com. Both site agents should read the conventions and this document. The decisions were agreed on 2 October 2026; live menu definitions were inspected that day. Each agent must check its current checkout and deployment before changing them.
Parks Computing already has a top-level Applets menu, as confirmed by its author. Keep it. The earlier suggestion to nest its launcher under Go is superseded. Both sites should order their site menus Site name, Go, Applets, View, Window, Help, omitting genuinely unused menus.
Both sites own their navigation, launcher catalog, identity entries, and window commands. Applets own their identity and working menus, with scoped additions to Go, View, and Help. The site bar remains stable as different windows come forward. The applet bar changes with the active content.
Both sites should retain direct launch access through Applets. Go holds navigation between destinations; Window lists existing windows. Launch behavior must state whether it creates an instance or activates one. Neither site should require a user to discover a launcher beneath a navigation submenu.
Hosts and applets should adopt PUDL 0.40.0 together with the migration guide. Declare stable menu IDs and use them as into keys. Translated labels then remain independent of routing. The release preserves applet shortcut scope for contributions, so Go, View, and Help contributions may declare applet-scoped shortcuts. A host Window title can opt into shared window management with data-menubar-windows; remove its duplicate handwritten management commands when doing so. Agents should use the tagged release rather than copying or patching PUDL internals.
The site should use the following division.
| Menu | Adoption guidance |
|---|---|
| Parks Computing | Keep Home, About Parks Computing, and Site settings. Move unrelated quick links into Go. Add Copy workspace link only with a label that distinguishes it from sharing one article or applet. |
| Go | Keep Find in the list and useful site destinations. Place the resume and other curated navigation links here where useful. Remove the nested applet launcher once the top-level Applets menu provides it. |
| Applets | Keep the direct launcher for tools such as Terminal, Files, Editor, Barcode Tool, Sudoku, and Theme Studio. Keep the order stable. A guide is documentation and belongs in Help, even when rendered through the same window machinery. Site settings belongs in the identity menu even if implemented as an applet. |
| View | Keep Window view, Classic view, and Theme. Append active-applet presentation controls under the applet’s heading. |
| Window | Keep bulk window actions, and provide clearly grouped active-window actions and an open-window list where supported. |
| Help | Provide site help and keyboard guidance. The Terminal Guide may remain permanently available as site documentation; active Terminal help must not duplicate the same command. |
Theme Studio should retain Theme Studio, File, Palette. Its identity menu already has About; add only supported identity operations. Keep opening and saving CSS under File and palette selection/reset operations under Palette. Add Edit only if actual editing-history or editing commands justify it.
Editor should use Editor, File, Edit, plus substantial domain menus when needed. Move word wrap, line numbers, and preview visibility into its View contribution. Put go-to-line navigation under Go and editor help under Help. Keep document close under File and window close in the identity menu.
Games and small tools should separate their identity entries from their working commands. For example, a game’s New game and Restart belong under Game. The commands() fallback now preserves working commands under Actions. Newly standardized applets should use menus() to give those commands a domain-specific title.
Articles should retain a recognizably named content group. PUDL 0.40.0 supplies scoped sharing and close labels. Since 0.49.0 an article has no File menu of PUDL’s, and its identity menu offers Print only where the site marks its page menu data-page-print, once its printed article is worth having. Sites should review any translation overrides that retain the old generic labels.
The site should use the same order and scope rules.
| Menu | Adoption guidance |
|---|---|
| YAVCHN | Provide Home and About YAVCHN. Put the source repository link in About or a clearly named support/development section. Remove the destination directory from this identity menu. |
| Go | Move Hacker News, Lobsters, Pinned stories, and Find the discussions of a link here. Clarify destination labels where an external source site could be confused with its YAVCHN view. |
| Applets | Retain direct access to Replies to me, Look up a user, and Who is hiring. Use an ellipsis when a command requires further input. |
| View | Keep story-list visibility, domain-filter access, and Theme. Domain filters should be labeled so their effect across story lists is clear. |
| Window | Retain bulk actions and provide active-window controls and the open-window list consistently with Parks Computing. |
| Help | Retain keyboard and site help. Label external Hacker News and Lobsters destinations clearly, and place ordinary external navigation under Go rather than treating it as help. |
The story reader should become Reader, Story, Discussion. Reader supplies identity, applet/content sharing, and Close window. Story keeps pinning, opening the original or source discussion, refreshing the article, hiding the story, and blocking its domain. A domain-block command must make its wider effect clear. Move Next story into a Go contribution headed Reader. Remove duplicate sharing and close commands after assigning their canonical locations.
Discussion retains its content-specific sorting, collapse, and expand commands. Move Next comment, Previous comment, and First new comment into the reader’s Go contribution. Reader presentation controls, if added, belong under View. Reader documentation belongs in Help’s Reader section.
Replies should use Replies, Watch. Watch holds Check now, Mark all as read, and Watch another user. Replies holds supported identity operations. Apply the same separation to the hiring and user-profile tools after inspecting their current menus; do not manufacture File or Edit menus for them.
The two site agents should compare their resulting menu inventories and share improvements through these documents. A shared convention or runtime behavior belongs in PUDL; domain wording and destinations belong in the respective site. Neither site needs to copy the other’s tool catalog or domain menus.