Everything an essay here can do

This file is a development fixture. It is marked draft: true, so it shows up while you run pnpm dev and is left out of every production build, the sitemap and the RSS feed. Its job is to prove the reading experience works before there are real words to read.

A paragraph should be easy to stay inside. The measure is about sixty-eight characters, the line height is generous, and links look like links without shouting. Italics and bold behave, and so does inline code.

A second-level heading

Headings are set in Fraunces, the same serif as the titles. They mark a change of subject, not a change of volume.

A pull quote is for the one sentence you’d underline. Use it once per essay, and mean it.

Lists

Things worth keeping short:

• Unordered lists for things with no order
• A second item, so the spacing is visible
  • And a nested one, because it happens

1. Ordered lists for steps
2. Where the sequence matters
3. And someone will follow along

Code

Technical writing is a first-class citizen. Blocks are highlighted at build time, so no JavaScript ships for them:

type Life = { freedom: number; obligations: string[] };

export function simplify(life: Life): Life {
  // Keep what compounds. Question the rest.
  return { ...life, obligations: life.obligations.filter(isWorthIt) };
}

pnpm dev      # write
pnpm build    # publish

A table

Element	Typeface	Used for
Display	Fraunces	Titles and headings
Text	Hanken Grotesk	Everything you read
Code	JetBrains Mono	Code

---

Images

Images take a caption when they need one. In MDX, use a normal Markdown image inside a <figure>:

That’s everything. Delete this file when the first real essay lands.