ID Identity · Design system · D1 to D100
One system for the store, portal and presentations. Build from it.
One token source feeds three surfaces. The decision log records why each rule exists, and the operational guides show how to apply it.
- Tokens
- ·
- React components
- ·
- Contrast checks
- ·
- Decisions
- ·
Design system sections
React
The package the public site is built from, rendered live rather than copied. Every specimen on that page is the real component.
85 components · 19 entry points · installed by tag
Razor
Review every partial DynamicWeb renders, in light and dark modes, with its contract and common implementation errors.
44 partials · cart, checkout, account
Layout
Use the named page tracks, 12-column grid and three standard split layouts.
5 widths · 12 columns · 4 breakpoints
Rules
Compare the correct and incorrect implementation of every rule.
38 documented rules · enforced by check:brand where measurable
Type
The production scale: Inter for reading, numbers and overlines, Instrument Sans for display, Chivo Mono for spec marks. Colour ramps sit underneath.
437 tokens · 82 contrast checks, 0 violations
The working principle
Specifications before adjectives. Numbers need evidence.
Slides
Set type for the room, protect the footer area and adapt web patterns for projection. The dealer deck is an output of this surface.
14 layouts · canvas 980 × 552 · dedicated type scale
Manual
Apply the voice, colour, typography, photography and platform guidance.
10 sections · behind login
Operations
Track open integration work and the maintenance procedures that keep the system operational.
VERIFY, spikes, STYRING.md
Decision log
Check what was decided, why it was decided and which parts of the system it governs.
100 decisions · D1 to D100
Start with the task
- Place content on a pageid-layout, id-cols, splits
- Shop homepagesix arrivals, D78
- Build a campaign pagehero, editorial-split, stats-band
- Build a product pagepdp, dual VAT, S to 6XL
- Send a dealer quotepartner room, known gap: no PDF
- Build a presentation14 layouts, one point per slide
- Present data or resultschart-bar, chart-plot, one y-axis
- OperationsVERIFY, spikes, STYRING.md
Latest decisions
The decision log records the rationale and binding scope. Each component has a .usage.md file with its contract and common implementation errors.
Three testable principles
01
Specifications before adjectives.
Use a measurable specification only when an approved product source provides it. If the evidence is missing, remove the claim.
02
Test under content stress.
Test every component with long localized text, Danish characters, sizes through 6XL and 200 table rows.
03
The accent has a job.
Use the signal colour only when attention has a consequence. If you cannot name the consequence, use a quieter role.