Complete styled systems.
WHAT THEY PROVIDE
A comprehensive set of components A coherent visual design A theming system Accessibility built in
WHAT THEY SUIT
Applications needing many components quickly Administrative interfaces and internal tools Teams without dedicated design resources
WHAT THEY COST
A recognisable appearance unless substantially themed Considerable bundle size Coupling to that library's conventions
WHAT TO DO ABOUT THE APPEARANCE
Theme it properly, through the provided system.
WHY NOT OVERRIDE
Overrides fight the library and break on upgrades.
WHAT TO CONFIGURE IN A THEME
Colours, type, spacing, radii, and component defaults.
WHAT TO CHECK
Whether unused components are excluded from the build.
WHY
Importing carelessly can include the entire library.
WHAT TO ESTABLISH
Which components your team may use, and which are wrapped.
WHAT WRAPPING PROVIDES
A single place to apply your conventions, and to replace the library later.
WHAT TO AVOID
Using library components directly everywhere, which makes replacement impossible.
