Have you ever been taught that “modularizing” CSS via an endless number of “reusable” object-like “classes” is the “proper” way to use CSS on “large-scale websites”, or have you taught others that these are “best practices”? Do you think there’s a difference between the term “large-scale websites” and “enterprise websites”? When I say “inheritance” and “specificity”, do you feel dirty?
If you answered yes to the above questions, then you, my friend, are going to absolutely hate this session.
"We're not designing pages anymore. We're designing systems of components." As with most things Stephen Hay says, he's right. Over the past few years, we've seen the Web community create style tiles, element collages, style guides, pattern libraries and a slew of other tools in order to break interfaces down to their atomic elements. Our interfaces are going more places than ever before, so this shift is essential to help us better understand what our websites consist of in order for us create smart, scalable, maintainable designs.
This session will introduce atomic design, a methodology for creating robust design systems. We'll cover how to apply atomic design to implement your very own design system in order to set you, your organization and clients up for success.
Brad Frost is a web designer. Follow him at http://twitter.com/brad_frost
Editor's Note: The "Scott" mentioned at the beginning is Scott McCloud, author of "Understanding Comics" - http://www.scottmccloud.com/2-print/1-uc/index.html
Follow Environments for Humans at http://twitter.com/e4h/
For more information, see http://environmentsforhumans.com/