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

DesignCraft

Rethinking color tokens, part 2

What we kept, what we cut, and why.

Rethinkingcolor tokens,part 2HALFTONE / JOURNAL
Bo Lindqvist
Published 2 min read

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. This post covers what we changed, why, and what it means for you.

#The constraint

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.

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.

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

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s

#What's next

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.

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

#Results

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

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.

text
# p95 before / after
build      41.2s -> 6.8s
deploy     18.0s -> 4.4s
end-to-end 11m   -> 1m 52s

#The details

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.

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.

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

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

#Rolling it out

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.

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. You notice them only when they are missing, usually at the worst possible moment.

  • Skip what has not changed
  • Keep the previous version one click away
  • Report problems in plain language

#Trade-offs

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.

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.

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.

Diagram of the request path before and after the change
Figure: the request path, before and after.
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