SAMPLE POST — What a longer article looks like

This is sample content. Delete this file (src/content/blog/sample-longer-post.mdx) or replace it with a real article.

This placeholder is long enough to trigger the automatic table of contents (it appears when a post has three or more headings), and it demonstrates code blocks with syntax highlighting.

Headings build the table of contents

Any ## or ### heading in a post is picked up automatically and linked in the “On this page” box above. No configuration needed — just write with headings and the TOC follows.

Code blocks are highlighted by Shiki

Fenced code blocks get syntax highlighting at build time, with zero client-side JavaScript:

def reading_time(text: str, wpm: int = 200) -> int:
    """Rough reading-time estimate, matching the site's own logic."""
    words = len(text.split())
    return max(1, round(words / wpm))

Inline code like npm run dev is styled too.

Images and quotes

Standard Markdown works everywhere. Blockquotes look like this:

Systems thinking beats heroics. Fix the process, and the outcome fixes itself.

Subheadings nest in the TOC

Third-level headings are indented in the table of contents, which keeps long technical posts scannable.

Wrapping up

Delete both sample posts once you’ve published something real — the blog index, RSS feed, and homepage “Recent posts” section all update automatically from whatever lives in src/content/blog/.