Skip to content
HalftoneJournal
← All articles

Design

In praise of our type scale

Good defaults, explained.

Eli Tanaka

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

What's next

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.

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.

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

  • Keep the previous version one click away
  • Run independent steps in parallel
  • Report problems in plain language
  • Cache what never changes

Rolling it out

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

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.

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

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

Where we started

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.

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.

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.

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

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

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.

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

What changed

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.

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.

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.

StepBeforeAfter
Install94s12s
Build41s7s
Deploy18s4s