Typography foundation
Six roles, two weights, one family. The type system the engine enforces — and the one this site is built on.
Type here is a system of roles, not a bag of sizes. You never reach for “14px” or “bold 24” — you reach for body or heading, and the size, line-height and tracking come with it. That is what keeps a hundred screens consistent and what lets the audit catch a heading that is really just big body text.
Every value below lives in one place: the @theme block in globals.css, exposed as Tailwind text-* utilities. Change a value there and it moves everywhere.
The scale
Each role carries its own line-height and letter-spacing — tracking tightens as the type grows, so large sizes stay optical and small sizes stay open. An explicit tracking-* still wins when a specific headline needs it.
caption13/18 · 0ui14/20 · 0title16/22 · 0heading24/30 · -0.02emdisplay40/44 · -0.02emhero64/64 · -0.03em| Role | Size | Line height | Tracking | Use for |
|---|---|---|---|---|
caption | 13px | 18px | 0 | Meta, labels, captions, code |
ui | 14px | 20px | 0 | Body copy, controls, table cells |
title | 16px | 22px | 0 | Lead paragraphs, card titles, subheads |
heading | 24px | 30px | -0.02em | Section headings |
display | 40px | 44px | -0.02em | Page titles |
hero | 64px | 64px | -0.03em | Marketing hero only |
Nothing sits below 13px. There is no step between display (40) and hero (64) on purpose — hero is a marketing-only flourish, not a sixth heading level.
Weight
Two weights, full stop: regular (400) for everything you read, medium (500) to mark a heading, a title or the one word in a sentence that carries the emphasis. No semibold, no bold, no light. Hierarchy comes from size, colour and space first; weight is the last and smallest lever, which is why two steps are enough.
Family
Inter carries body and UI (--font-sans) — an open, neutral grotesque that stays readable at small sizes. Inter Tight, the tighter display cut, carries headings (--font-display, applied to h1/h2) so titles read with a little more density than the text beneath them. IBM Plex Mono (--font-mono) is reserved for code, IDs, commands and raw values. Numbers run tabular-nums everywhere so figures line up in tables and stats.
Readability
- Measure. Body text wraps by ~68 characters (
max-width: 68ch). Long lines are the fastest way to lose a reader. - Minimum size. 14px for anything you read as a sentence; 13px is the floor, for labels and meta only.
- Contrast is paired with the grey ramp. Body is
ink-2(6.3:1 on white), primary text isink(15:1), andink-4is decorative — never body. Size and colour move together: lighter greys only on larger or secondary text. - Line-height loosens as size tightens. Body gets room (20/14 ≈ 1.43); hero is set solid (64/64) because display type needs none.
Do / Don’t
| Do | Don’t |
|---|---|
Pick a role by meaning (heading, body) | Pick a pixel size to hit a look |
| Build hierarchy with size → colour → space | Reach for bold to make something matter |
Keep body at ui/14px and ~68ch wide | Set long paragraphs in 13px or full-width |
| Let the role’s tracking stand | Add per-element tracking without a reason |
Developer handoff
The whole foundation is these tokens. Paste them under @theme (Tailwind v4) and the text-caption … text-hero utilities carry size, line-height and tracking together:
--text-caption: 13px; --text-caption--line-height: 18px; --text-caption--letter-spacing: 0em;
--text-ui: 14px; --text-ui--line-height: 20px; --text-ui--letter-spacing: 0em;
--text-title: 16px; --text-title--line-height: 22px; --text-title--letter-spacing: -0.01em;
--text-heading: 24px; --text-heading--line-height: 30px; --text-heading--letter-spacing: -0.02em;
--text-display: 40px; --text-display--line-height: 44px; --text-display--letter-spacing: -0.03em;
--text-hero: 64px; --text-hero--line-height: 64px; --text-hero--letter-spacing: -0.04em;Use :root instead of @theme if you aren’t on Tailwind — the variable names are identical, you just wire the utilities yourself.
How it’s kept
This isn’t a style guide you’re trusted to remember. The engine audits real interface code against it: too many families, a type size off the scale, body text under the minimum, or more than two weights all surface as findings. The rules behind those checks — and the evidence for them — live in the taste spec, and your agent reads them before it writes a line of UI.