Typography
Gelium typography is a token contract, not a page-specific scale. These server-rendered specimens read the active theme (theme-material or theme-basecoat) and the active light/dark class. Use the same role for the same job; do not tune a heading with a new font or arbitrary pixel value.
Scale and measure
The decomposed tokens make size, weight, line-height, letter-spacing, and family inspectable. Body prose stays at a readable 65ch measure; Gelium adapts the roughly 68ch USWDS and 30em GOV.UK guidance to one stable docs contract.[1][2]
Design with intent
A clear hierarchy helps people scan
Gelium keeps body copy calm and legible. Put one idea in each paragraph, keep the line length bounded, and let the theme provide the family.
LABEL · STATUS · SUPPORTING METADATA
Rules
TYPE-ROLE: choose display, headline, title, body, or label by content job, then use the matching--ui-type-*alias.TYPE-MEASURE: keep reading content near65ch; let controls and data tables use their own layout measure.TYPE-RHYTHM: preserve the token line-height; do not compress body text to fit a card.TYPE-THEME: theme overrides the decomposed values; consumers keep the alias so Material and Basecoat stay interchangeable.
Sources and Gelium adaptation
- W3C WCAG 2.2, 1.4.12 Text spacing: Gelium leaves room for user text-spacing overrides instead of clipping prose.[3]
- GOV.UK type scale: Gelium adopts stepped, responsive-friendly roles rather than a fluid novelty scale.[1]
- USWDS typography: Gelium adapts readable measure and explicit type tokens to CSS custom properties.[2]
See also: Tokens, Themes, Accessibility.