Design system operations
Maintain the system
OPGAVER.md covers page, campaign and quote tasks. This page tracks open integration work and points to the maintenance procedures.
Counts come from public/design/manager.json and the same committed sources checked by CI. A new VERIFY flag appears after the next pnpm manager build.
Current status
- Phase
- ·
- VERIFY
-
·
· tied to a spike step
- Spike answers
-
·
of 10 questions
- Decisions
-
·
latest ·
Open integration work
P1 to P7 and P9 to P11 are complete without a DynamicWeb instance. Ten binding questions remain in docs-dw/spike.md. Each answer closes specific VERIFY flags. S5 and S6 may reshape an adapter; the other answers require a rename or documented fallback.
| Step | Question | Answer | Flags | Rework if different |
|---|
Parked with a reason
Six parity gaps depend on a DynamicWeb spike answer. Keep them parked until the platform binding is verified.
Maintenance tasks
Each task names the source, generated outputs and common failure points. Full procedures are in STYRING.md.
- Add an iconicons.json, pnpm icons
- Change a colour, font or spacing valuetokens/*.json, never output
- Add a componentpartial or packages/ui
- Close a VERIFYevidence first, flag later
- Run the DW spikeS1 to S4 before the data form
- Add a brand rulecheck:brand, correct/incorrect
- Write a decisionappend-only, with binds
System inventory
These counts come from the current source. Every partial must have a matching .usage.md contract.
- Partials
-
·
0 without usage
- Brand rules
-
·
enforced by check:brand
- Icons
-
·
governed set, D37
- Tokens
-
·
core brand, light mode
- Contrast checks
-
·
of ·, 0 violations
- Templates
-
·
cshtml in IDSystem