# Design system A design system is a living set of documents specifying [[Design principles]], [[Design guidelines]], and UI components for a product or organization. UI components are often organized into a [[Component library]] with accompanying code examples. Design systems are often made up of: 1. [[Design principles]] 2. [[Design guidelines]] (i.e., style guide) 3. [[Component library]] These components can be assembled to build any number of applications, helping teams expedite and scale their productivity in a consistent manner. Design systems are a product serving other products, made up of many parts. As such, it’s important to [[Version individual components rather than an entire design system]]. --- A design system is a set of self-imposed constraints that allow us to make decisions faster. https://nathanbeck.eu/essays/addicted-to-every-possibility/ Types of constraints - Engineering - Business - Design Each of the design leads would also be the ones who are identifying the needs of the design system, ensuring that all the designers under each of their purview are adhering to the design system, so the design may essentially become the folks who are ensuring adherence to the design system --- [[Creating a design system]] [[Example design systems]] --- Reference - [[Zack Rutherford]]. “Design Systems vs. Pattern Libraries vs. Style Guides - What’s the Difference?” *Studio by UXPin*, 29 Sept. 2017, [www.uxpin.com/studio/blog/design-systems-vs-pattern-libraries-vs-style-guides-whats-difference/](http://www.uxpin.com/studio/blog/design-systems-vs-pattern-libraries-vs-style-guides-whats-difference/). Accessed 1 Mar. 2021. Read later - [Useful Sections for a Design System Reference Site](https://superfriendlydesign.systems/articles/useful-sections-design-system-reference-site/?ref=heydesigner) - [Hey Design Systems!](https://heydesign.systems/)