ahmido
3eff4d8579
## Summary - add the Spec 325 artifacts for screenshot-anchored strategic target images - update the UI/UX enterprise audit documents to capture strategic surfaces and grouped follow-up candidates - add supporting follow-up specs, target experience briefs, and target image assets for the audit workflow ## Testing - not run (documentation/spec artifact changes only) Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #385
134 lines
6.0 KiB
Markdown
134 lines
6.0 KiB
Markdown
# Workspace Overview Target Experience Brief
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Surface IDs | UI-001, UI-002 |
|
|
| Route | `/admin` -> `/admin/workspaces/{workspace}/overview` |
|
|
| Source screenshot | `../screenshots/desktop/ui-001-workspace-overview.png` |
|
|
| Source page report | `../page-reports/ui-001-workspace-overview.md` |
|
|
| Target sidecar | `../target-images/target/workspace-overview-target.md` |
|
|
| Primary persona | Workspace owner / MSP operator |
|
|
| Secondary personas | Manager, support reviewer |
|
|
| Repo-truth posture | Source route and screenshot are `repo-verified`; target composition is direction only. |
|
|
|
|
## Current-State Snapshot
|
|
|
|
The page already reads as a calm workspace home with operational and governance attention cards. The current page report says several valuable paths compete at the same level: choose environment, operations, alerts, backup attention, recovery attention, findings, and hygiene.
|
|
|
|
## Current-State Productization Problems
|
|
|
|
- Primary next action is not singular enough for a first landing page.
|
|
- Backup, recovery, alerts, and assigned work compete instead of laddering from posture to next action.
|
|
- Evidence and diagnostics are present, but the proof path is not visually distinct from navigation.
|
|
|
|
## Target User Promise
|
|
|
|
In five seconds, a workspace owner knows whether the workspace needs action, which environment needs attention first, and where the evidence trail lives.
|
|
|
|
## First-Five-Seconds Target
|
|
|
|
Show a single workspace posture band, one dominant "Review priority environment" action, and a short attention queue with reason and evidence link.
|
|
|
|
## Primary Decision
|
|
|
|
Which workspace-level item needs operator attention first?
|
|
|
|
## Primary Action
|
|
|
|
Review priority environment.
|
|
|
|
## Secondary Actions
|
|
|
|
Open operations, review governance inbox, inspect backup readiness, review audit trail.
|
|
|
|
## Target Information Hierarchy
|
|
|
|
1. Workspace context and posture.
|
|
2. One priority decision with reason and impact.
|
|
3. Environment attention list.
|
|
4. Evidence and OperationRun traceability.
|
|
5. Secondary diagnostic summaries.
|
|
|
|
## Main-View Keep / Promote / Simplify
|
|
|
|
| Treatment | Elements |
|
|
| --- | --- |
|
|
| Keep | Workspace name, environment count, governance/backup/recovery attention, active operations. |
|
|
| Promote | Priority environment, reason, impact, evidence link, primary action. |
|
|
| Simplify | Equal-weight card grid, repeated navigation links, diagnostic counts without a decision role. |
|
|
|
|
## Detail Drawer Treatment
|
|
|
|
Use a right-side detail drawer for selected environment attention. It should show reason, evidence basis, recent runs, and diagnostics in separate sections.
|
|
|
|
## Advanced/Admin Treatment
|
|
|
|
Workspace settings, member management, raw health diagnostics, and configuration shortcuts stay behind secondary links or menus.
|
|
|
|
## Hidden/Removed Default Elements
|
|
|
|
Hide raw operation payloads, provider error IDs, and repeated "open" links from the default view.
|
|
|
|
## Target Layout Direction
|
|
|
|
Use a wide decision header, left priority queue, right evidence/operations strip, and lower secondary domain summaries. Avoid decorative dashboard charts.
|
|
|
|
## Visual Target Direction
|
|
|
|
Calm dark command surface with ivory text, warm graphite panels, mint as a narrow action accent, amber for attention, and restrained violet for evidence links.
|
|
|
|
## Status/Trust Model
|
|
|
|
No green success state unless the underlying state is verified. Separate execution state, governance attention, and backup/recovery posture.
|
|
|
|
## Dangerous Actions
|
|
|
|
No destructive action should be primary on the workspace home. Downstream backup/restore/provider actions must disclose mutation scope before execution.
|
|
|
|
## Customer-Safe Review Notes
|
|
|
|
Not customer-facing by default. Any customer-shareable summary must hide diagnostics and raw provider details.
|
|
|
|
## Workspace/Environment Context
|
|
|
|
Workspace is explicit in the header. Environment-specific items must show the environment name before any action link.
|
|
|
|
## Empty / Loading / Error States
|
|
|
|
Empty state should say no environments are ready for review and offer one setup action. Loading should preserve the workspace shell. Error state should explain whether workspace context, environment data, or operations data failed.
|
|
|
|
## Accessibility Notes
|
|
|
|
Priority items need visible labels beyond color. The primary action must be reachable by keyboard before secondary links.
|
|
|
|
## Repo-Truth Classification
|
|
|
|
| Target element | Classification | Notes |
|
|
| --- | --- | --- |
|
|
| Workspace route and source screenshot | repo-verified | Spec 323 browser pass reached the route. |
|
|
| Workspace attention cards | repo-verified | Present in page report as current content class. |
|
|
| Priority environment queue | plausible-existing | Derived from existing attention concepts, needs runtime data verification. |
|
|
| Evidence strip | foundation-only | Audit/evidence surfaces exist, but exact workspace aggregate needs later spec. |
|
|
| Final brand tokens | spec-only | Spec 325 direction, not final brand governance. |
|
|
|
|
## Screenshot-Anchored Image Prompt
|
|
|
|
Start from `ui-001-workspace-overview.png`. Create a target design direction, not runtime implementation. Preserve the workspace-home purpose. Fix competing next actions by showing workspace posture, one primary priority-environment action, reason/impact, evidence link, and secondary operations/governance/backup summaries. Keep diagnostics secondary. Use calm dark enterprise styling with Tenantial mint as an accent. Avoid generic blue SaaS, fake compliance claims, green success without verification, placeholder nonsense text, decorative charts, and runtime implementation claims.
|
|
|
|
## Implementation Pattern Requirements
|
|
|
|
- Use an explicit workspace context header.
|
|
- Keep one dominant next action.
|
|
- Separate governance, operation, and backup/recovery state.
|
|
- Link evidence and OperationRun proof without making diagnostics primary.
|
|
|
|
## Later Implementation Candidate
|
|
|
|
Workspace and Environment dashboard productization.
|
|
|
|
## Non-Goals For Later Implementation
|
|
|
|
Do not add new workspace metrics, new persisted posture truth, or a dashboard framework without a separate spec.
|