Some people say design is like science and I think they’re on to something. You see, these past weeks I’ve been working a lot with defining design systems and I couldn’t help but see the resemblance.
Years ago, we defined the scope of projects by how many pages the site had. The more pages, the bigger the project. Now while that makes sense in theory, it doesn’t make sense in reality. A designed webpage is actually made up out of different sets of “bricks”. Think: Subway sandwich pieces that you can combine into different delicious combinations.
Atomic design is a methodology composed of five distinct stages working together to create interface design systems in a more deliberate and hierarchical manner.
The stages that Brad outline are:
- Atoms are the basic building blocks of it all – they include things like buttons, form labels, inputs, and other similar elements.
- Molecules are simple groups of UI elements functioning as a unit – think of a search form that consists of a button, a form label, and an input field.
- Organisms are bigger UI components combining both atoms and molecules. This could be the header of a webpage that consists of a logotype, a navigation, and a search form.
- Templates combines different organisms into a functioning whole – think of a wireframe. It has all the organisms in place, but there’s no actual content there yet. This is the blueprint or skeleton of a page.
- Pages are the final stage – they shows what the template looks like with real representative content in place.
While I’m currently working on two projects that are very different in terms of pages (one is nearly 10,000 pages and the other is less than 5 pages), they both require a solid design system to make sure we’ve got all the stages covered from the start.
If you’re interested in learning more about design systems, feel free to e-mail and I’ll be sure to answer!
Here’s some great further reading on the topic:
Atomic Design by Brad Frost
Cooking with Design Systems by Dan Mall
Setup a design system by Marco Lopes