In this post Amit stresses how we should be making our colours in the code of our design systems human-readable and how we can go about doing it.
Paul shares with us the benefits they've found at eventmobi by having their prototypes be part of their style guide.
Matheus shows us, using something like web components or React.js, we could be exposing the API of a component rather than the classes to avoid misinterpretation and the copying and pasting of classes from one component to another.
In this first part of a series, the pros, the cons, and the pitfalls of sharing a sketch file using a cloud service are delved into.
There will come a time when a component in your design system needs to 'retire'. Paul talks us through the motions of doing this as cleanly as possible in a large project codebase.