A Design System Is What It Does

The US Web Design System is headed for a major overhaul, and the author thinks shadcn/ui may be where it lands. That part is still speculation. But if it happens, the real story isn’t the framework swap. It’s the shift in what government sites are trying to be.

Start with the text. USWDS’s default typography keeps lines shorter, at about 68 characters, while shadcn’s default typeset stretches closer to 83. That sounds small until you try to read it. Shorter lines are easier to scan, easier to read for people with lower vision, and better suited to pages whose main job is to present information clearly. Longer lines push the other way.

That difference matters because government sites are mostly text and forms. USWDS was built around that reality. Its prose component is meant for content that comes out of markdown or a CMS, and the documentation doesn’t just show you settings. It shows you a full kitchen-sink example with headings, lists, tables, spacing, and vertical rhythm, basically teaching you how the component is supposed to be used.

And the docs go further than “here are the knobs.” They explain the typography principles behind the defaults and why usa-prose “just works.” shadcn’s typeset documentation, by contrast, is described as flexible and helpful for tweaking, but lighter on the why. It tells you how to configure things, including how to make text bigger for accessibility, yet it doesn’t really argue for the defaults or spell out reasonable values. The examples show structure, but not much guidance on what that structure is for.

That’s the heart of the argument. A design system isn’t just code; it’s a set of defaults that steer teams. USWDS nudges people toward readable, information-heavy pages without much effort. shadcn gives you the tools to get there, but only if someone on the team already knows what “there” should look like. For a startup that may be fine. For the long tail of government teams, it sounds like extra work dressed up as flexibility.