Interactive route
scaleUse the interactive route to explore this foundation live.
foundations / type and scale
Type and Scale
DK uses scale ratios and text measurements as first-class inputs so type stays consistent across systems and densities.
Principles
Core principles
These are the design-system rules this foundation should reinforce.
- Typography should scale from one ratio system, not ad hoc size picks.
- Measure, rhythm, and line breaking matter as much as font size.
- Density changes should feel intentional, not like generic compact mode.
Model
How DK models it
This section connects the concept to the actual DK math and token pipeline.
- Type sizes and spacing steps derive from named scale ratios in the theme seed.
- Text tooling measures contrast, line breaking, and spacing recommendations together.
- Component recipes consume tokenized sizes rather than freehand values.
Practice
How to use it in product work
These are the decisions designers and engineers should make with this foundation in mind.
- Choose a ratio that matches the product voice, then let headings, body, and component chrome inherit from it.
- Use the same scale family for field heights, button sizes, and layout gaps.
- Treat compact presets as a full-system decision, not just smaller padding.
Proofs
What the proof layer guarantees
These are the reliability claims DK makes about this foundation today.
- Components are checked against target sizes and estimated inline containment.
- Scale changes do not bypass the proof layer just because the visuals still look plausible.
- Type-heavy surfaces like Table and DatePicker remain comparable across presets.
Token notes
- Scale tokens inform type size, spacing, control heights, and some radius/elevation ladders.
- Preset ratio names are surfaced in the design-systems comparison workspace.