Skip to content
HalftoneJournal
← All articles

DesignCraft

How we design our type scale

What we kept, what we cut, and why.

Cam Okafor

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

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.

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

  • Cache what never changes
  • Report problems in plain language
  • Skip what has not changed
  • Run independent steps in parallel

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.

  • Cache what never changes
  • Keep the previous version one click away
  • Run independent steps in parallel
  • Skip what has not changed

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.

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

What we measured

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.

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.

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.

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.

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}/` };
}