explore the design intelligence archive
Daily digestDesign systems are products. This hub tracks token strategies, component API changes, accessibility guidance, and governance patterns from teams shipping at scale — including public-sector and enterprise references worth studying. Primary sources (release posts, spec updates, conference talks) are summarised with flags for established practice versus early adoption. Ideal for UI designers, design technologists, and anyone maintaining a library their engineers actually use.
Google's Material Design continues to push token-based theming as the default way to build flexible, on-brand components — it's the clearest real-world example of tokens done at scale. For juniors, understanding tokens beats memorising any one system's components.
material.io
Google's Material 3 Expressive update layers more personality — motion, colour, shape — onto Material's existing token structure without a rebuild. It's a solid case study in how mature design systems evolve.
design.google
Penpot now bundles native design tokens and shared component libraries into its open-source platform at no cost — a feature set that's often gated behind paid tiers elsewhere. Design tokens themselves are a well-established practice, just newly accessible without a licence fee.
penpot.app
The Penpot-vs-Figma debate is really about who controls your design system's tokens and infrastructure. Self-hosting is now a real option, not just a theory.
designsystemscollective.com
Penpot's 2025 enterprise comparison shows teams increasingly picking design platforms based on data control and token portability, not just feature parity with Figma.
penpot.app
Also worth exploring: Design tools · UCD methods
