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

Design

In praise of our type scale, part 3

How we chose, tested and shipped the details.

In praise ofour typescale, part 3HALFTONE / JOURNAL
Ada Rivers / Eli Tanaka
Published 2 min read

Consistency is a feature you ship once and maintain forever. Our lint rules now catch one-off sizes and colors before they reach review. This post covers what we changed, why, and what it means for you.

#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.

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

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.

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

#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.

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

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.

“A cache key must include everything that can change the output, and nothing that cannot.”
Jun Calder

#Trade-offs

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 constraint

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.

“A cache key must include everything that can change the output, and nothing that cannot.”
Hana Pike

#Results

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.

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.

ts
export async function publish(post: Post) {
  const problems = validate(post);
  if (problems.length) return { ok: false, problems };
  await commit(post);
  return { ok: true, url: `/blog/${post.slug}/` };
}
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