Marcus Andrey Study
Ler em português Library

Framework · Design systems · 3 min read

Atomic design

Brad Frost's five stages (atoms, molecules, organisms, templates, pages) for thinking about an interface as parts and wholes, so you can see what to build once, what to combine, and where real content tests the system.

  1. 1 Atoms
    What
    The smallest parts that still mean something
    For example
    A label, an input, a button
  2. 2 Molecules
    What
    A few atoms doing one job together
    For example
    A search form
  3. 3 Organisms
    What
    Larger sections built from molecules
    For example
    A header with logo, navigation and search
  4. 4 Templates
    What
    Organisms placed in a layout, no real content
    For example
    A question page layout
  5. 5 Pages
    What
    Templates with real content, to test the parts
    For example
    A real booking with a very long name

The stages work at the same time, not one after another.

Brad Frost's five stages of atomic design, from the smallest parts to real pages.

Use it when

  • A team needs a shared language for "how big" a piece of interface is before deciding who owns it.
  • You run an interface inventory and want to group what you found from small parts to whole screens.
  • Components work alone but break when real content fills a page.

How to use it

  1. Find the atoms. The smallest parts that still mean something on their own: a label, an input, a button, an icon. Tokens sit below them. Output: a list of atoms, each linked to the tokens it uses.
  2. Group atoms into molecules. A few atoms that do one job together, like a label, an input and a button forming a search form. Output: molecules with a single, clear job.
  3. Build organisms from molecules. Larger sections of an interface, like a header made of a logo, navigation and the search form. Output: the sections people recognise on a screen.
  4. Place organisms in templates. A template is the page layout with components in place and no real content yet. It shows the structure. Output: one template per page type.
  5. Fill templates with real content to make pages. Long names, empty lists, error states, translated text. Pages are where you find what the parts didn't plan for. Output: a list of fixes that go back to the atoms, molecules and organisms.
  6. Move back and forth. When a page breaks, change the part that caused it, then check the page again. The stages are not a waterfall. Output: parts that survive real content.

Worked example

Harbour, the design system of the ferry company Tidewater, uses the stages to plan its booking flow.

Stage In Harbour
Atoms Button, Text field, Icon, Label
Molecules Passenger row (label, text field, remove button)
Organisms Ticket card, Summary list with Change links
Templates "Book a crossing" question page: header, one question, Continue
Pages The real booking for the 07:40 sailing, with a passenger named Maria-Fernanda dos Santos Albuquerque

The page showed the problem: the long name broke the Ticket card. The fix went back to the organism (the name now wraps on two lines), and every page that uses the card got it.

Watch out for

  • Treating the stages as a build order. Building all atoms first, then all molecules, delays the moment you learn from real pages.
  • Arguing about the label. Whether something is a molecule or an organism matters less than whether it has one owner and one doc page.
  • Folders named after the stages. People look for "Ticket card", not "organisms". Name components by what they are.
  • Skipping pages. Templates with placeholder text hide the long names, empty states and translations that break components.

Template

Use this to sort what an interface inventory found, then check one real page against it.

Stage       | Part                  | Built from               | Owner   | Doc page?
------------|-----------------------|--------------------------|---------|----------
Atom        | ...                   | tokens: ...              | ...     | yes / no
Molecule    | ...                   | atoms: ...               | ...     | yes / no
Organism    | ...                   | molecules: ...           | ...     | yes / no
Template    | ...                   | organisms: ...           | ...     |
Page        | ...                   | template + real content  |         |

Real-content check on the page:
  Longest name / label: ...      breaks? ...
  Empty state: ...               breaks? ...
  Error state: ...               breaks? ...
  Other language: ...            breaks? ...
Source
Brad Frost, "Atomic Web Design" (blog post, 2013) and Atomic Design (book, 2016, free online).
Where to find it
Design Systems in Practice: From components to patterns › What a pattern is
UX Design Foundations: What a design system is › Atomic design

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close