Here's a great article around the different layers of the design system. One that I really agree with is the 'recipe layer'.
which contains composed UI components to be used consistently across specific contexts (like a product or product family), but aren’t reusable across the entire organization.
Anecdotally we did something similar at 99designs, and it worked really well. Essentially they are just smaller UI component libraries that built off the core design system. It's almost like an incubator.
This works really well at allowing you to slow down and only bring in versatile, proven, and useful components into the design system [[20231027111000-design-system-speed]]. Until then, teams still have all the benefits of sharing code, and the DS team isn't a bottleneck.
[[20220704124529-design-system-harvesting]] [[20220808103811-spotify-encore]] [[20211122112956-design-system-component-hierarchy]]
https://shinytoyrobots.substack.com/p/the-hub-and-spoke-design-system-model
Keywords: expansion packs, design system ecosystem
[[20220704011551-tiered-design-systems]]
[[architecture]] [[components]] [[designsystem]] [[designsystemapi]] [[designsystembranding]] [[product]]