Skip to content
NewSee how fast an edit goes live on this site
Halftone

Design

In praise of color tokens, part 2

Good defaults, explained.

In praise ofcolor tokens,part 2HALFTONE / JOURNAL
Dee Marsh
Published 2 min read

Good defaults are invisible. You notice them only when they are missing, usually at the worst possible moment. This post covers what we changed, why, and what it means for you.

#Trade-offs

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

We started from the text. Body copy sets the rhythm for everything else, so we fixed its size and line height first and derived the rest of the scale from there.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#The details

We tested each change with the people who use the product all day. The best feedback was rarely about how something looked, and almost always about how it felt to repeat.

Hairlines carry more structure than you would expect. A single one-pixel rule can replace a card, a shadow and a background, and the page gets quieter.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s

#The constraint

Consistency is a feature you ship once and maintain forever. Our lint rules now catch one-off sizes and colors before they reach review.

Motion should explain, not decorate. If an animation does not tell you where something came from or where it went, we remove it.

Good defaults are invisible. You notice them only when they are missing, usually at the worst possible moment.

“Measure the time from done to live, and treat every minute of it as a bug.”
Dee Marsh

#What we would do differently

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

We started from the text. Body copy sets the rhythm for everything else, so we fixed its size and line height first and derived the rest of the scale from there.

Diagram of the request path before and after the change
Figure: the request path, before and after.

#Rolling it out

We tested each change with the people who use the product all day. The best feedback was rarely about how something looked, and almost always about how it felt to repeat.

Hairlines carry more structure than you would expect. A single one-pixel rule can replace a card, a shadow and a background, and the page gets quieter.

Consistency is a feature you ship once and maintain forever. Our lint rules now catch one-off sizes and colors before they reach review.

“Good defaults are invisible until they are missing.”
Ivo Santos

#Results

Motion should explain, not decorate. If an animation does not tell you where something came from or where it went, we remove it.

Good defaults are invisible. You notice them only when they are missing, usually at the worst possible moment.

Every color in the product now maps to a role, not a hue. Designers pick "border" or "muted text", and the system decides what that means in light and dark mode.

How we designour typescaleHALFTONE / JOURNAL

Design4 min

How we design our type scale

What we kept, what we cut, and why.

Cam Okafor
In praise ofour typescaleHALFTONE / JOURNAL

Design10 min

In praise of our type scale

Good defaults, explained.

Eli Tanaka