Sanity
Why It's In The Canon
Sanity.io earned its place by doing something rare in developer tooling: treating the brand surface as an editorial problem, not a UI component problem. Their site uses display type with actual confidence — large, high-contrast, editorially paced — at a time when most SaaS products were collapsing into the same Inter-on-gray aesthetic. That choice matters because it proved the hypothesis: developer tools don't have to look like developer tools. You can hold typographic tension, use scale to create rhythm, and still ship a product that engineers trust.
The specific thing to study is the hierarchy. Sanity's typography doesn't treat every level of information the same way. Headlines do editorial work; body type does functional work; they don't bleed into each other. That separation — knowing when type should attract and when it should disappear — is the craft. For anyone building platforms, content tools, or design systems, this is a case study in how type decisions compound into brand perception before a single word is read. The aesthetic vocabulary they established influenced a generation of headless CMS and creative infrastructure products. Understanding why it landed is more useful than copying it.
