# All channels
Your Sketch library is not a design systemFebruary 3, 2018 at 8:15pm
be sure to keep your eye on the prize: creating a beautiful, flexible, reusable collection of frontend components that can be used to build real software.
February 6, 2018 at 2:13am
February 6, 2018 at 1:31pm
I completely see the benefit of having the output of a design system as actual code. BUT I also think that it's not a requirement. After all, one can create a design system for print only for instance. I think the most important things people tend to ignore about design systems is that systems have input and output. The system should describe how the input (requirements, ideas) is turned into output (in the example above, it is component code). Ideally, when creating such a system, it should be closed loop system, where the output is evaluated and used to create new input.
I agree with the sentiment here.. but also agree with - A design system can/should be more than just components. Language, personality, rules, etc. that can't necessarily be seen in a component library. I do however long for the day that I can design using real life component library (we're using React) instead of the static tools like Sketch. This might be doable today, but I personally lack the knowhow or proper tool to do so.
I wasn't considering Print, but I agree with your feedback loop principle. I've learned recently how much work is involved in moving from a visual style guide to a true system for building UI.
My version of design system is a living collection of designed, documented and coded UI components which has that feedback loop from the designers and engineers building products with the system.