Blog

Design tokens for teams without a designer

You don't need a design team to look deliberate — you need about a dozen named decisions and the discipline to stop making new ones at midnight. How we keep a loud, eclectic site coherent with CSS variables.

Most sites built without a designer don't look undesigned — they look over-designed: five grays that almost match, three button radii, an accent color that mutates between sections. Each decision was reasonable in the moment it was made; the page is the archaeology of those moments. The fix is not hiring taste. It is making every visual decision once, giving it a name, and refusing to make it again at midnight inside some component file.

That is all design tokens are: opinions with names. Ours live in a dozen CSS custom properties, and they are the reason a deliberately loud, eclectic site stays coherent while being maintained by people who write SQL for a living.

The dozen decisions

The rules that do the designing

Borrowing taste, legally

The initial decisions still require taste, and taste can be borrowed deliberately: pick one site whose mood matches your ambition and reverse-engineer its restraint — count its colors (fewer than you think), measure its spacing, notice what it refuses to do. One source is inspiration with discipline; five sources is the mud you were escaping. We did exactly this: studied the energy we wanted, then rebuilt it from our own tokens, with our own weirdness where it pays rent.

A developer team with twelve named decisions and three rules ships something coherent enough that visitors assume there is a design team. There is — it just met once, wrote everything down as variables, and went back to shipping.