Road Runner Rules: More What You'd Call Guidelines for Design Systems


Details
Wouldn’t it be great if we could spend less time trying to style the markup we’ve been handed, and more time creating a system of smart, reusable design components?
Well, we’re in luck. With the increased popularity of pattern libraries and the proliferation of templating languages, we finally have the tools to create and deploy our own design systems.
But what is a design system, and how do we create them? What rules should it follow? How do I get my team on board?
In this talk I will be pulling wisdom and insight from my past two years of creating a design system for Redhat.com. I will explain what we call our “Road Runner Rules”, which influence every piece of code that we write.
I’ll be covering topics such as:
- What is a Visual Language
- Single Responsibility Principle
- Single Source of Truth
- Single-selector CSS with BEM
- Atomic Modular Design Systems
- Style Guides
- Pattern Libraries
It doesn’t matter if you are a designer who wants to learn how to turn your visual language into a design system, or a developer who wants to create more modular components, you’ll want to sit in on this session and learn from the successes and failures of creating a large scale design system.
------------------------------------
6:30pm - Pizza and drinks
7:00pm - Intros and General business items
7:05pm - Speaker
7:50pm - QA and hangout
About our Speaker:
Micah Godbolt, frontend architect, author, podcaster, trainer and speaker at worldwide open source events, is often found promoting frontend architecture, Sass, visual regression testing, and schema-based design at his blog, micahgodbolt.com. A Pacific Northwest native, he currently lives outside of Portland, Oregon with his wife and two children.
Pick up a copy of Frontend Architecture for Design Systems from O’Reilly press at fea.pub

Road Runner Rules: More What You'd Call Guidelines for Design Systems