The newsletter’s working title, “Taking Things Apart,” never nouned — a real name needed to span all four pillars, survive an inbox from-line, and sound like the person writing it. Candidates fell one by one for the baggage they’d bring: unintended violence, a crowded namespace, an unrelated academic movement. It became Knolling — laying every part out square and visible — with the old title demoted to tagline.
The favicon shipped next, but only partly on purpose: Mark A, the four-square “knolling grid,” went out; Mark B and the wordmark lockups stayed explicitly deferred until they had somewhere real to attach to — an account, finished brand tokens.
A short brand pass then closed out the remaining open decisions: keeping “workshop” and “field notes” as display names, since they already read as parallel subjects sitting in the nav; keeping the colophon at the URL it was already live at rather than renaming it for a more precise word; and shipping a real wordmark lockup.
Once the Buttondown account for Knolling actually existed, Mark B and its lockup shipped for real — and building the social avatar for that account surfaced a genuine rendering bug that had been quietly living in the favicon assets since Mark A shipped: an SVG-to-raster tool silently off-centering marks, caught only by measuring pixels instead of trusting a preview.
Main takeaways
- A newsletter name needs to survive four unrelated pillars and an inbox from-line — description-first names don’t noun the way an actual name has to.
- Deferring an asset until it has somewhere real to attach to beats shipping it against nothing.
- “Looks right in a preview” and “is actually correct” are different claims.
What I got wrong
- Shipped the first favicon assets on a visual preview alone; they were quietly off-center the whole time.
- The wordmark lockup was never validated against a real external use case — “correct by construction” isn’t the same as “looks right in the wild” until something actually uses it.
