2.4 KiB
UI-001 Workspace Overview
| Field | Value |
|---|---|
| Route | /admin -> /admin/workspaces/{workspace}/overview |
| Source | WorkspaceOverview, WorkspaceOverviewBuilder, WorkspaceHubRegistry |
| Area / scope | App shell / workspace |
| Archetype | Overview / Dashboard |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | ../screenshots/desktop/ui-001-workspace-overview.png |
| Browser status | Reached through local smoke login; redirected to workspace route. |
First Five Seconds
The page clearly communicates a workspace home with operational and governance attention cards. The strongest next action is not always singular because several cards and links compete: choose environment, operations, alerts, backup attention, recovery attention, and findings links.
Productization Review
- Decision-first: strong, with attention cards ahead of diagnostics.
- Evidence-first: partially present through counts and posture explanations.
- Context: workspace shell is explicit and no environment is selected.
- Customer/auditor safety: not customer-facing, but copy is calm and mostly productized.
- Diagnostics: recent operations are correctly framed as diagnostic rather than governance health.
Information Inventory
Default-visible content includes workspace identity, environment count, governance attention, backup/recovery attention, active operations, alert failures, assigned work, and hygiene state. Status/trust signals distinguish calm, affected environments, and diagnostic activity. Empty states are mostly honest.
Dangerous Actions
No destructive action was visible on the first viewport. Main risk is false affordance or multiple equal-weight primary links, not immediate mutation.
Scores
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 4 | 4 | 4 | 4 | 4 | 3 | 4 | 3 | 3 | 4 | 4 | 4 |
Top Issues
- Several high-value links compete for primary action hierarchy.
- Backup/recovery counts need a target mockup that separates posture, evidence, and next action.
- Responsive behavior was not captured in Spec 323.
Target Direction
Keep as P0 strategic target. Later mockup should preserve the calm workspace-first hierarchy while making one next action dominant and keeping diagnostic activity secondary.