What a page
can be

There are two kinds of thing on this site, and they want opposite treatment.

A note is a unit of thinking. It should look like every other note, because the interesting variation is in the links between them, not the typography. When I write about the strategic staircase, the page’s job is to disappear.

A story is different. The form carries part of the argument. Robin Rendle’s essays do this — the layout isn’t decoration on top of the writing, it is some of the writing.

What this page gives up: nothing

This is the part worth noticing. This page has its own document, its own stylesheet, its own typography — no site chrome reached it. And it is still a normal member of the garden:

Those links above aren’t hardcoded. They’re relref, resolved at build time against the content graph — so if a note’s title changes, or its slug moves, this page follows. And if a target disappears, the build fails rather than shipping a dead link.

Proof it works in both directions: here’s a book I read — Wintering — and a film, The Boy and the Heron. Different types, different templates, same graph.

The one rule that still applies

Raw HTML blocks in markdown cannot contain blank lines. CommonMark ends the block at the first gap and reparses the rest as markdown, which is how a hand-built <div> ends up dumping its own source onto the page as code.

Look at the source of this file: every HTML block above is blank-line-free. Not a style preference — a hard requirement.

When to reach for this

Rarely. A story costs more than a note: it’s authored in the repo rather than Obsidian, it needs its own CSS, and it can’t be revised as casually. That price is worth paying when the layout is doing argumentative work, and not otherwise.

The default should stay boring. This is the exception, and exceptions earn their keep by being rare.