docs(spelwork): Part 2 — sketches for the three §6 dashboards #224
No reviewers
Labels
No labels
build-dist
priority
P1
priority
P2
priority
P3
priority
P4
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Toilville/toilville-design!224
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/171-dashboard-sketches-part2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #171, #172, #174. Closes nothing.
Scope
Adds the Part 2 deliverable for the three §6 dashboards. Four new files, no edits to existing files:
Brand/specs/spelwork/spelwork-dashboard-design-part2.mdBrand/specs/spelwork/spelwork-dashboard-part2/worker-health.pngBrand/specs/spelwork/spelwork-dashboard-part2/task-in-progress.pngBrand/specs/spelwork/spelwork-dashboard-part2/system-wide-problems.pngPart 1 left §6 at "not started", blocked behind §3 (warning states) and §4 (step names). Both are now decided, and the sketches follow the decisions:
color.accent.success, slow =color.accent.warning, broken =color.accent.error, very serious =color.accent.critical(new).oldis the stale, data-freshness state, on a neutral incolor.neutral.warm-*(new), outside the severity ladder.color.safety.*stays rejected for worker health.spel.stage.0tospel.stage.5. The step colour is one sequential brand-blue lightness ramp.No token values are drafted yet.
color.accent.critical, the stale-neutral token (its exact name is not decided) and the step ramp still need to be drafted, so the sketches draw no severity or step colour and name each missing token on the figure. System-wide problems is built onAttentionSummary, which ships, and carries no invented metric.Screenprint is exploratory, not an approved production dashboard theme. The language is still being developed, and the dashboards may not use it at all. The figures settle the information architecture, content hierarchy, semantic separation and contract-backed data usage. Open dependencies are listed in §5 of the document.
Testing
Documentation and images only. No code, tokens or generated files change, so
just buildandjust checkhave nothing new to verify. Review the document and the three figures.Impact Statement
No effect on tokens,
dist/or any consumer. This gives #171 a reviewable starting point and records what #172 and #174 still need to supply before the sketches can use final colours.