Notes on Building a Quieter Web

This piece first ran in my newsletter before it landed here — hence the canonical override in its frontmatter, pointing back at that original issue rather than at this page’s own address. It’s a useful example of the other half of the canonical-URL story: sometimes the original isn’t this site, and the frontmatter needs to say so explicitly.

Quiet as a design constraint

Most reading surfaces on the web are optimized for something other than reading: engagement loops, ad density, “time on page.” The result is a familiar kind of loud — autoplay motion, notification badges, related-content rails competing with the actual sentence you came for.

A quiet interface makes a different set of trade-offs:

• A measure narrow enough that your eye doesn’t lose the line (65–75 characters, not the full viewport width).
• Type sizes and line-heights tuned for sustained reading, not for cramming more above the fold.
• Motion that respects prefers-reduced-motion rather than assuming everyone wants the transition.
• A palette that recedes — no gradients competing with the text for attention.

None of this is novel. It’s closer to what reading surfaces looked like before growth metrics got involved.

Why it matters for a canonical home

If this site is where every piece originates before it syndicates elsewhere, the reading experience here sets the tone for everything downstream. A newsletter can’t inherit good typography from its source, but it can inherit the discipline of what got written — shorter paragraphs, fewer asides, a piece that was edited for a quiet page rather than padded for an infinite-scroll one.