FAQ

Yes. Every page you see is a plain .md file under content/, read at build time — no database, no CMS. Editing a file, committing, and pushing to main rebuilds and redeploys the live site. The Style Guide shows everything the Markdown supports.

Drop a new file in content/projects/. The filename becomes the slug (field-notes.md → /projects/field-notes), and the frontmatter title and order decide how it shows in the index. Tags are optional and feed tags.

By design. The theme follows your operating system via prefers-color-scheme — the whole UI is driven by CSS tokens, so it flips automatically. One less switch to think about.

That's the plan. The engine is stable and only the content/ folder changes per site, so it can become a GitHub template or a create- scaffolder. The Roadmap tracks where that's going.

The ⌘K palette is backed by a small index built at compile time from the same Markdown — titles, headings, and body text for every page, project, and post. It's fetched lazily, so it never weighs down the initial load.