Parent
Outcome
Make the dashboard a dependable control plane rather than a collection of independently rendered operational pages. Establish durable state, a coherent resource hierarchy, fast navigation, and shared safe interaction patterns.
Why now
The dashboard already covers 30+ server and serverless pages, but navigation is a small mode switch, state is split between config and local files, and each page reimplements loading, mutation feedback, confirmation, polling, and error handling. New delivery, team, fleet, and audit features need a stable foundation first.
UX direction
- Responsive application shell with explicit project/environment/service context.
- Permission-aware navigation with breadcrumbs and durable deep links.
- Keyboard-first search and actions without making discoverability keyboard-dependent.
- Standard loading, empty, stale, degraded, error, success, retry, and destructive-confirmation states.
- WCAG 2.2 AA behavior, reduced-motion support, mobile layouts, and focus restoration.
Existing work incorporated
Children
Exit criteria
All later roadmap areas can use one persisted control-plane model, one operation/event model, one authorization boundary, and one documented UI interaction system.