How This Site Is Built
The stack and the reasoning behind this site: static Astro, Markdown-first publishing, and one deliberate constraint that makes writing the only thing that takes effort.
If you want to actually keep writing, the decision that matters is not your stack. It is making everything except the writing boring. So that is what this site is built to do: pick deliberately dull technology, and let publishing be the only thing that takes any effort.
It is a static build. No server, no database, almost no JavaScript shipped to you, the reader. Do it this way and the site stays fast and cheap enough to keep online indefinitely, which is exactly what you want from something meant to be a durable, citable archive rather than a thing you babysit.
Make each piece a Markdown file with a typed front-matter block, and let the build fail loudly when a required field is missing, so a broken page never ships:
title: 'Weeks to One Day: Catalog Automation Across Ten Product Lines'
description: 'What multi-line catalog automation actually looks like.'
pubDate: 2026-06-28
pillar: 'results'Take the slug from the filename and never change it once published. That permanence is the point: any copy you post elsewhere can point its canonical link back to the version here, so this stays the source of record no matter where it gets mirrored.
The original lives here. Everywhere else is a mirror.
The payoff is the workflow. Adding a piece means dropping a file in the right folder and pushing to the repository. There is no CMS to log into, nothing to configure, no friction between the thought and the publish. And that is the whole trick, the one worth stealing for whatever you build: the less the tooling asks of you, the more consistently the writing actually happens.