Skip to content

docs: UI navigation rework vision (draft, future)#55

Draft
offendingcommit wants to merge 2 commits into
mainfrom
docs/ui-navigation-rework
Draft

docs: UI navigation rework vision (draft, future)#55
offendingcommit wants to merge 2 commits into
mainfrom
docs/ui-navigation-rework

Conversation

@offendingcommit
Copy link
Copy Markdown
Owner

Captures the future UI/navigation direction discussed 2026-06-02. Draft — not scheduled; needs a brainstorming pass before implementation.

  • Collapse the Dashboard/Fleet overlap into a hierarchical Server → Workspace → Peers/Sessions/Conclusions drill-down (outline view).
  • Fleet folds into the Dashboard as an all-servers view, workspaces labelled <workspace> (<server>), filterable by server (overlay, not a separate page).
  • Standalone Fleet possibly repositioned as a settings/ops view.
  • Open questions (instance selector vs Server node, routing, settings-Fleet contents, responsive) listed for the brainstorming session.

Separate concern from the CORS-proxy work in #54.

Draft future-spec: collapse Dashboard/Fleet overlap into a Server > Workspace >
Peers/Sessions/Conclusions drill-down with an outline view; Fleet folds into the
Dashboard as a server-filterable overlay, with standalone Fleet possibly becoming
a settings/ops view. Not scheduled — needs a brainstorming pass before build.
Add a verified current-architecture map (routes, Sidebar, Dashboard/Fleet, data
layer, instance store) with file references, the target Server>Workspace>section
IA, phased action items (Phase 1 merge Dashboard/Fleet is settled; Phases 2-3
need brainstorming), validation steps, open questions, and conventions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant