DESIGN SYSTEM — LIVING DOCUMENT

The system, on the record.

Every color, type ramp, and texture on this site comes from one tokens file. This page renders straight from it — so if the site drifts, this page drifts with it.

Why publish this

A style guide that lives in a Figma file goes stale the day after it ships. This one can't. The CSS, the OG images, and the swatches below all read from the same tokens.json — one source of truth, three consumers. Publishing it does two things: it keeps me honest, and it doubles as a QA harness. Every block type in the CMS appears in the gallery below with real sample content, so if a block breaks, I see it here first.

The aesthetic is "national-park poster meets engineering notebook" — warm paper, evergreen ink, and just enough mountain to remember where it was built.

Front-end developer turned product builder.

Heading two — Fraunces

Heading three — Public Sans 600

Body copy set in Public Sans. The quick brown fox jumps over the lazy dog, then heads west on the Colorado Trail toward the divide.

MONO EYEBROW — JETBRAINS MONO · 39.7392° N

--shadow-xs
--shadow-sm
--shadow-md
--shadow-lift
topo — territory
ridge-a
ridge-b
ridge-c
paper grain — atmosphere

The never-combine rules

Four motifs, used with restraint. The rules that keep it from turning to soup:

  • Topo and ridgelines share a viewport only in the hero and footer — nowhere else.
  • Topo contours never sit under body copy, cards, or photos. Territory, not wallpaper.
  • Duotone imagery never lands on top of topo or ridgeline fills.
  • Never more than two non-grain motifs in a single view. Paper grain is atmosphere; it doesn't count.

Grain is atmosphere, topo is territory, ridgelines are punctuation, duotone is content.