A library with ten components needs no rules. A library with four hundred components and twenty contributors needs a few good ones.
1. One Owner per Library
Shared ownership often means no ownership.
Name a maintainer for each library who reviews changes and keeps the structure consistent.
2. Group by Purpose
Organize pages by what components do — Inputs, Navigation, Feedback — rather than by who made them or when.
3. Use Properties Instead of Copies
Every duplicated component is a future inconsistency.
Component properties and variants cover sizes, states and optional parts in a single, searchable component.
4. Deprecate Before You Delete
Mark outdated components as deprecated and point to their replacement.
Give teams a release or two to migrate before removing anything.
5. Document in Place
A short description on every component answers most questions before they're asked: when to use it, when not to and what it replaces.
A library with ten components needs no rules. A library with four hundred components and twenty contributors needs a few good ones.
1. One Owner per Library
Shared ownership often means no ownership.
Name a maintainer for each library who reviews changes and keeps the structure consistent.
2. Group by Purpose
Organize pages by what components do — Inputs, Navigation, Feedback — rather than by who made them or when.
3. Use Properties Instead of Copies
Every duplicated component is a future inconsistency.
Component properties and variants cover sizes, states and optional parts in a single, searchable component.
4. Deprecate Before You Delete
Mark outdated components as deprecated and point to their replacement.
Give teams a release or two to migrate before removing anything.
5. Document in Place
A short description on every component answers most questions before they're asked: when to use it, when not to and what it replaces.
