This site is a static export built from a small automated pipeline. Content is written as plain markdown, bundled into a typed index at build time, and rendered as fully static pages. No database, no server-side rendering at request time, no external analytics.
The flow
- Write a markdown file in `content/` with a `title`, `date`, and `summary` in the frontmatter.
- Build runs a small script that inlines every post into a typed content index, then Next.js exports the static pages.
- Deploy ships the `out/` directory to a host that serves the files as-is.
The news section is meant to be regenerated on a schedule, pulling or generating fresh briefing content so it stays current without manual effort.
Why this approach
Static output is fast and cheap, and it keeps the whole thing simple to operate. The content is plain text I actually own, in a format that will outlive any framework. If the tooling changes next year, the markdown stays.