February 7, 2022
Design
Blog post read time icon
2
 min read

Using Atomic Design

UX/UI design can get incredibly messy with even small projects. To help keep things organized, I utilize a design system called Atomic Design which was invented by Brad Frost.

As with many other designers, I’ve made my own modifications to Atomic Design. In the content below, I’ll talk about how I work with this design system.

Atomic Element Layout

In traditional Atomic Design the element types are Atoms, Molecules, Organisms, Templates, and Pages.

This is my modification to the elements:

  • Brand Styles
  • Atoms (a) — “Small” elements such as buttons, input fields, or user profile photos
  • Molecules (m) — “Medium” elements such as inputs with labels, various button states, or user profiles with stats next to them.
  • Organisms (o) — “Large” elements such as a user’s profile card, a contact form, or a section of a website
  • Templates (t) — Entire pages that can have slight variations in different situations such as a user profile before their email is verified and then after their email is verified.
  • Archive (x) — This is where all of the elements that you are no longer using go, just in case you need to re-access them in the future.

Naming Convention

Having a standard naming convention is incredibly important to keep things organized in your Sketch, Figma, etc file. I subscribe to the idea that this naming system should be simple, yet flexible to meet any situation.

My naming system typically follows this structure:

(type: atom, molecule, etc) / (class: button, input, etc) / (subclass A: state, color, size, etc) / (subclass B: state, color, size, etc)

As a general rule, I don’t like to drill down more than 4 times in an element’s “name” (type / class / subclass A / subclass B). This helps reduce the amount of time to find a certain symbol when you are looking for it. To help keep elements within this framework, I use dashes for very similar classes instead of breaking them into subclasses.

For example:

m/input-text/small/filled

  • Element Type = m
  • Class = input-text
  • Sub Class 1 = small
  • Sub Class 2 = filled

If you have any questions or are looking for a designer, feel free to reach out: https://www.danstrangfeld.com/contact

Get an email for new posts

Other articles

Design Process

I view design as an evolving process in which the client and the designer collaborate to find the best solution for the problem at hand. Just as nature has gone through evolution over billions of years, design should follow the rules set forth by this process. A principle that I always work with in mind: Good design = evolving design. With that being said, let’s jump into...

Read time icon
4
 min read

How to Make Your Startup look like a Fortune 500 Company

Everyone loves great design whether they know it or not. At the core, design passively influences decision making which means that your designs can determine your business’s fate. Bold claim? Nope. Think about it like this: you are researching the best CMS software for your sales team and run across a startup that claims to have the best CMS product that has EVER been invented because of its advanced machine learning, AI, and (insert cliche startup tech here). BUT, their website, marketing materials, and branding look like they've hired an intern, blindfolded them, and promoted them to lead designer. Subconsciously, you’ve immediately judged the quality of this startup’s product as soon as you’ve seen how they present themselves through...

Read time icon
8
 min read

Pitch Deck Handbook: Business Model Slide

The Business model slide is where you help investors gain clarity on how you make money. It includes; revenue models, unit economics, and who you are selling to. This slide is typically placed after the Solution Slide or the Why Now Slide.

Read time icon
2
 min read