Design System Docs Are Becoming Invisible Infrastructure
Source: Sorted Pixels
Meta's Astryx approach—embedding design tokens and components directly into developer workflows rather than maintaining a separate documentation site—reflects a growing recognition that beautiful design system websites don't change behavior if teams never visit them. The shift mirrors how successful infrastructure (payment rails, authentication, CDNs) succeeds by disappearing into products rather than demanding constant consultation; design systems win when they're frictionless dependencies, not destinations. This reframes design system ROI from "did we build something pretty and comprehensive" to "did we reduce decision-making friction and enforce consistency without friction," which changes how organizations staff and measure these efforts.