front-of-the-front-end and back-of-the-front-end web development
A distinction we need to build successful web things.
A distinction we need to build successful web things.
“A design system doesn't need 300 people involved right out of the gate. Give a small, smart, and scrappy team the time, resources, and autonomy to get things properly set up. Things will grow over time, but start small.”
What the difference between the two means for design systems.
A small change in our mental model of design systems can make a big difference.
A breakdown of the pros and cons of each strategy.
“The heart of design systems has nothing to do with button colors and everything to do with how human beings work together.”
“Your health is more important than your deadline.”
How a three-tier design token architecture can support different flavors of themeability.
“Web components vs. React, Angular, Vue, Svelte, or whatever is a false dichotomy.”
“Sometimes the most productive thing you can do is sleep.”
“The specific design, technology, and tool choices your design system makes are very rarely the reasons why it will succeed or fail.”
“The machines will undoubtedly impact the world of design systems.”
“It can’t be said often enough: ‘a prototype is worth a thousand meetings.’”
“There’s a strange irony that as the web medium is getting more capable and multi-dimensional, the web design field seems to be getting more constrained and one-dimensional.”
Company-wide UI orchestration for designers and developers.
Let’s launch a universal library of common UI components!
How AI can enhance your design system efforts.
Web creators debate adopting a worldwide design system.
How recipes enhance the ecosystem of your design system.
Crap is inevitable, but how to deal with it?
“‘Should designers code?’ is a funny question now.”