## 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
1.9 KiB
Markdown
49 lines
1.9 KiB
Markdown
# UI-010 Baseline Profiles
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Route | `/admin/baseline-profiles` |
|
|
| Source | `BaselineProfileResource` |
|
|
| Area / scope | Governance / workspace-owned analysis |
|
|
| Archetype | Drift / Diff |
|
|
| Design depth | Strategic Surface |
|
|
| Repo truth | repo-verified |
|
|
| Screenshot | `../screenshots/desktop/ui-010-baseline-profiles.png` |
|
|
| Browser status | Reached through workspace route. |
|
|
|
|
## First Five Seconds
|
|
|
|
The page is a baseline library. It needs to make the reusable standard, snapshot truth, assignment state, and compare readiness clearer than a generic admin resource.
|
|
|
|
## Productization Review
|
|
|
|
- Decision-first: medium; library behavior is visible but product purpose needs clearer framing.
|
|
- Evidence-first: snapshot and compare links should be central.
|
|
- Context: workspace-owned, not environment shell.
|
|
- Customer/auditor safety: not directly customer-facing.
|
|
- Diagnostics: capture/compare evidence should be available on demand.
|
|
|
|
## Information Inventory
|
|
|
|
Default content should include profile status, capture mode, latest snapshot, assignment count, compare posture, and next action.
|
|
|
|
## Dangerous Actions
|
|
|
|
Capture, compare, archive, and baseline assignment changes are high impact. They need confirmation, authorization, audit, and OperationRun continuity.
|
|
|
|
## Scores
|
|
|
|
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|
|
| ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: | ---: |
|
|
| 3 | 4 | 3 | 4 | 3 | 3 | 4 | 3 | 3 | 4 | 3 | 4 |
|
|
|
|
## Top Issues
|
|
|
|
1. Generic resource feel hides the product role of baselines.
|
|
2. Snapshot truth and assigned-environment impact need stronger hierarchy.
|
|
3. Dangerous capture/compare actions need target-state review.
|
|
|
|
## Target Direction
|
|
|
|
P1 strategic target for governance baseline library and domain pattern for related create/edit/detail pages.
|