5 tips to know before building a design system

As a main developer or occasional contributor to several design systems, open source or internal, I’ve made some mistakes in the way. Let’s help frontend developers planning to start a design system or contribute to it not to fall into the same errors. Building your own design system sounds like a great idea, but keeping it alive, maintained & useful is a challenge.

Main content points: 1: Do we really need a design system? 2: Audit your codebase 3: Make product agnostic components 4: Document, plug & play 5: Adoption