
Design systems
Design systems small teams can maintain
Most design systems fall apart when the person who built them leaves. Here is how we set ours up to last.
Most design systems fall apart when the person who built them leaves. Here is how we set ours up to last.
Start smaller than you think
A system with 40 well-documented components is more useful than one with 300 that nobody understands. We start with the components your product uses every day.
Write docs for engineers
Every component has a short page with when to use it, when not to, and a link to the code.
Give it an owner
One designer and one engineer own the system
Changes are reviewed once a week
Every release has a short changelog