How this site is built (and how I publish to it)
A Markdown file, a git push, and Vercel does the rest. No CMS to maintain, and nothing to log in to.
Synopsis. A portfolio and build journal where every post is a Markdown file in the repo, published by pushing to GitHub.
The publishing model
Every post is a single .mdx file in content/journal/. The frontmatter at the top holds the title, date, tags, and the Build Specs card. The body is ordinary Markdown.
To publish: save the file, commit, and git push. Vercel notices the push, rebuilds the site, and the post is live.
Scheduling posts
A post only appears once its date has arrived, so I can write a batch now and let them go out one per day. The site re-checks every hour. In npm run dev, drafts and future-dated posts always show, so I can preview them.
Why not a CMS
I like writing in an editor and keeping everything in git. Posts get version history and diffs for free, and there's no admin login to secure.
The best tool for publishing is the one I never have to think about.
What's next
More entries to come. Each one follows the same template, so the specs are easy to skim.