ahmido
8a889a863e
## Summary - add the Spec 323 Tenantial enterprise UI audit foundation package - add the UI/UX audit registry artifacts, templates, and supporting brand context placeholder - update Spec Kit prompts/templates plus PR fast-feedback guardrails for ongoing UI productization coverage ## Scope - docs-first audit foundation only - no runtime Laravel, Filament, Livewire, route, auth, or database behavior changes intended ## Validation - [x] `git diff --check` - [ ] application test suite run ## Notes - primary spec: `specs/323-tenantial-enterprise-ui-audit-foundation/` - this branch also updates `.gitea/pull_request_template.md`, `.gitea/workflows/test-pr-fast-feedback.yml`, and `scripts/check-ui-productization-coverage` to make the coverage gate durable for future UI work Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #383
49 lines
2.3 KiB
Markdown
49 lines
2.3 KiB
Markdown
# UI-002 Environment Dashboard
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/workspaces/{workspace}/environments/{environment}` |
|
|
| Source | `EnvironmentDashboard`, managed-environment widgets |
|
|
| Area / scope | Environment dashboard / environment-bound |
|
|
| Archetype | Overview / Dashboard |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified |
|
|
| Screenshot | `../screenshots/desktop/ui-002-environment-dashboard.png` |
|
|
| Browser status | Reached with local Spec 180 smoke fixture. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page makes the selected environment visible and shows backup/recovery posture. It is clear that the operator is inside an environment, but several posture, verification, backup, and recovery messages compete for what should happen first.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: strong but dense.
|
|
- Evidence-first: good evidence/posture signals, but proof hierarchy needs simplification.
|
|
- Context: workspace + environment route is explicit.
|
|
- Customer/auditor safety: operator-facing; customer-safe language should be checked before reuse.
|
|
- Diagnostics: verification and health details should stay progressive.
|
|
|
|
## Information Inventory
|
|
|
|
Default content includes environment name, backup health, recovery readiness, operations, verification/reporting widgets, and navigation to environment-owned resources. Status signals include stale/non-healthy backup posture and recovery evidence concerns.
|
|
|
|
## Dangerous Actions
|
|
|
|
Likely downstream actions include backup, restore, permission checks, provider fixes, and baseline compare. Target design must show mutation scope before action: TenantPilot only, Microsoft tenant, or simulation only.
|
|
|
|
## Scores
|
|
|
|
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|
|
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
|
|
| 3 | 3 | 4 | 4 | 3 | 3 | 4 | 3 | 3 | 4 | 4 | 4 |
|
|
|
|
## Top Issues
|
|
|
|
1. Too many domain signals appear with similar weight.
|
|
2. Backup truth and recovery evidence need clearer separation.
|
|
3. Dangerous downstream actions need impact/confirmation/evidence review in target mockup.
|
|
|
|
## Target Direction
|
|
|
|
P0 individual target mockup. The page should become the environment command surface: one primary posture decision, secondary domain drilldowns, and diagnostics behind deliberate disclosure.
|