Do you design digital products (or websites) and hand design files off to developers for implementation? If you answered yes, settle in! While the should-designers-code debate rages on, we're going to look at how adding a methodology to your design workflow can make you faster, more consistent, and loved by all developers... even if you don't code.
- "Atomic" is a browser-based timeline animation tool.
- "Atomic Design" is a design methodology in which you design very small parts and combine them in larger and larger pieces to build a whole.
- "Atomic CSS" is a system in which you apply styles directly through designated HTML classes.
- "Project Atomic" is something for running containerized applications, like Docker? I dunno it's DevOps-y and above my head.
- "Atomic Web Browser" is an old (looks abandoned) iOS web browser.
None of them have anything to do with each other, at least conceptually.
The following is a guest post by Nick Berens, a senior front-end developer at wisnet.com. Nick and his team have been building websites through custom style guides for years. Over those years, Nick has been building and evolving a tool to help with this process. I'll let Nick explain both the philosophy and the tool.