Writing about the things I build

Lead paragraph. This is the opening of a writeup — slightly larger, used to set the stakes for whatever we're about to explore.

Body paragraph. Bold text emphasizes a term, italic offers a lighter stress, and links look like this. You'll see inline.code() used constantly in writeups — function names, flags, paths. Strikethrough exists too.

A second-level heading

Writeups lean on a strict heading hierarchy: H1 once, H2 for main sections, H3 for steps or sub-sections, H4 only if things get deep.

A third-level heading

Short intro under the sub-section. Then we usually get into a list, a code block, or a table.

An H4 (used sparingly)

Rare, but styled so nested sub-points stay legible.

"The best code is the code you don't have to write."
— every automation obsessed dev, ever.

Unordered list with a nested child:

• First bullet
• Second bullet with a nested list
  • Nested item one
  • Nested item with inline.code
• Third bullet

Ordered list:

1. Scaffold the thing
2. Ship the boring parts first
3. Revisit when you have data

Code blocks

Fenced code block, syntax highlighting comes later (Shiki + github-dark in Phase 2):

export async function load({ platform }) {
  const source = createContentSource(platform);
  const posts = await source.listPosts({ limit: 5 });
  return { posts };
}

You can also press Ctrl + K to open the search palette (once we add one).

Tables