Why this blog lives in git
A short note on keeping writing close to the code: versioned, reviewable, portable, and easy to ship.
This blog is intentionally simple: one file per post, stored next to the rest of the site, reviewed through git, and shipped by the same deploy pipeline.
That shape keeps the writing durable. The source stays portable, every edit has history, and there is no separate CMS account to keep alive.
The authoring loop
Write the post in content/blog, add frontmatter for the metadata, preview locally, then commit it. The site turns that file into a static page with canonical metadata, Open Graph data, JSON-LD, sitemap entries, and RSS.
The useful constraint
Static writing rewards clarity. A post can still be rich with MDX, but the default path is plain text, links, headings, lists, and code blocks. That is enough for most field notes.