Design system components, recipes, and snowflakes | Brad Frost
"When should we make something a component?" is a question I've been fielding for years. My strong answer: right from the start. Creating things with a component-based mindset right out the gate saves countless hours and wailing and gnashing of teeth. Everything is a component. But there's some n
Design system components, recipes, and snowflakes “When should we make something a component?” is a question I’ve been fielding for years. My strong answer: right from the start . Creating things with a component-based mindset right out the gate saves countless hours and wailing and gnashing of teeth. Everything is a component. But there’s some nuance to this. Where each component lives matters. In my client design system work, we’ve arrived at some vocabulary that helps determine where any component should live. Design system component – Accordion ! Button
Explore this link on the map →saved by
related reading
- Building a Design System from scratch - The Blog of Maxime Heckelblog.maximeheckel.com
- Design System Wisdom 2023cianfrani.dev
- Devouring Detailsdevouringdetails.com
- Impeccable: The missing upgrade to Anthropic's impeccable skillimpeccable.style
- Say precisely what you mean.index.how
- Designing Systems | Atomic Design by Brad Frostatomicdesign.bradfrost.com
- Wonder Blocks: on the creation of Khan Academy’s design systemdesignsystems.com
- Multiple Layers of Abstraction in Design Systems | Spotify Engineeringengineering.atspotify.com
- The Making of the Figma Pattern Library | Figma Blogfigma.com
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- How a small team built Figma.com’s design systemdesignsystems.com
- getdesign.md — DESIGN.md collection for AI coding agentsgetdesign.md