The Platform Is Part of the System

A well-crafted design system is only half the argument. The other half is where it lives.

I spend my working hours thinking about components, tokens, states, and the invisible scaffolding that makes a product feel considered. But a system is only as good as its distribution — the mechanism that gets it in front of the people who need it, in a form they'll actually return to. A brilliant component library buried in an unmaintained Confluence page has failed at design just as thoroughly as a beautiful button nobody can find on the page.

Publishing is a design decision

Choosing a platform is choosing constraints, the same way choosing a grid or a type scale is choosing constraints. A CMS with clumsy authoring flow will quietly punish long-form thinking. A rigid template will flatten nuance into the same five shapes every time. The platform isn't neutral infrastructure sitting underneath the "real" design work — it's exerting design pressure on every piece of content that passes through it, whether or not anyone chose it on purpose.

The system extends past the file

Product designers are trained to trace a system end to end: token to component to pattern to product. Publishing deserves the same discipline. The right platform doesn't just hold your words — it reinforces the same clarity and care your design system already promises. Get both right, and neither one has to compensate for the other.