webui: group the navigation and split Configuration into System pages #1488

Closed
opened 2026-10-27 13:40:36 +00:00 by sam · 0 comments
Owner

The nav is a flat bar of 11 routes. Skills, Curators and Channels are
capability-hidden on the reference deployment, so the eight visible items are
the best case; with every capability on it wraps.

Decisions (Sam, 2026-09-20):

  • Five top-level items: Dashboard, Work, Agent, Events, System. The last four
    are dropdowns.
  • Items are renamed now that the group carries the context: Event inspector →
    Inspector, Field mappings → Mappings, Playbook bindings → Bindings.
  • Each dropdown item explains itself ("inspect incoming events", "map incoming
    event data to custom fields").
  • Configuration dissolves into real routes under /system/*, not anchors into
    one long page. It is currently ~10 sections and 4021px tall.

See docs/prds/dashboard-navigation-groups.md.

Notes

Completed locally: System menu keeps Status, Logs, and Appearance as operational items, followed by a visible Settings divider and Task settings, Models, Repositories, Channels, and Advanced. Appearance preferences now use a Pinia store, render as a desktop 2x2 grid with controls beneath labels, stack on mobile, and persist theme/density/motion/tooltips. Desktop/mobile visual inspection, browser interaction/reload checks, Impeccable layout detector, and full task check pass.

Close reason

Navigation grouping and Pinia-backed Appearance slice implemented and fully verified.


Imported from beads archie-core-ocfm · GitHub #965 · type feature · priority P1 · created 2026-09-20 · closed 2026-09-20

The nav is a flat bar of 11 routes. Skills, Curators and Channels are capability-hidden on the reference deployment, so the eight visible items are the best case; with every capability on it wraps. Decisions (Sam, 2026-09-20): - Five top-level items: Dashboard, Work, Agent, Events, System. The last four are dropdowns. - Items are renamed now that the group carries the context: Event inspector → Inspector, Field mappings → Mappings, Playbook bindings → Bindings. - Each dropdown item explains itself ("inspect incoming events", "map incoming event data to custom fields"). - Configuration dissolves into real routes under /system/*, not anchors into one long page. It is currently ~10 sections and 4021px tall. See docs/prds/dashboard-navigation-groups.md. ### Notes Completed locally: System menu keeps Status, Logs, and Appearance as operational items, followed by a visible Settings divider and Task settings, Models, Repositories, Channels, and Advanced. Appearance preferences now use a Pinia store, render as a desktop 2x2 grid with controls beneath labels, stack on mobile, and persist theme/density/motion/tooltips. Desktop/mobile visual inspection, browser interaction/reload checks, Impeccable layout detector, and full task check pass. ### Close reason Navigation grouping and Pinia-backed Appearance slice implemented and fully verified. --- _Imported from beads `archie-core-ocfm` · GitHub #965 · type feature · priority P1 · created 2026-09-20 · closed 2026-09-20_
sam added the highfeature labels 2026-10-27 13:40:36 +00:00
sam self-assigned this 2026-10-27 13:40:36 +00:00
sam closed this issue 2026-10-27 13:40:36 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1488