Marketing pages

Naming components so nobody asks twice

A naming scheme for components, variants and props that designers and developers both read the same way.

Johnny Bell

Published in Software Engineering

A component name is read hundreds of times a day, by designers in a panel and by developers in code. If the two read it differently, every handoff starts with a translation.

  • Name what it is, not what it looks like: Alert, not Red box.
  • Variants describe a choice: size, colour, state.
  • Props use the same words as variants, in the same order.

It sounds pedantic. It saves hours every week.

Share this post

From the blog

The latest industry news, interviews, technologies, and resources.