I started this repo because I wanted a place to publish projects, then kept rebuilding it until it could actually support the kind of technical writing and project history I wanted to put on it.

This series is a short history of that evolution: from a basic static site, to a more structured Gatsby content system, to notebooks and plugin work, to maintenance fights, to the recent blob-storage, editorial tooling, and LLM-assisted writing workflow.

The series is dated from the repo’s first commit in 2019, but the story itself runs through the more recent editorial and LLM work in 2026.

What to expect

Each article focuses on one problem arc rather than trying to retell the entire git history.

1. From Static Site to Publishing System — how the site started, why I outgrew the first version, and what I learned from the migration. ~6 min read
2. Inventing a Content Model for Real Projects — tags, series, clusters, and stronger page-generation rules. ~6 min read
3. Publishing Dense Technical Work Without Watering It Down — notebooks, embeds, and richer technical writeups. ~6 min read
4. Owning the Seams: Plugin Forks and Toolchain Drift — dependency breakage, vendoring, and maintenance reality. ~7 min read
5. Turning the Site into a Portfolio Editorial Machine — blob storage, Obsidian support, and the repo becoming an authoring workbench. ~6 min read
6. LLM Tooling for Portfolio Writing — repo-history synthesis, quality reporting, and turning a vague editorial backlog into concrete next steps. ~7 min read

The through-line is pretty simple: every time the tooling got in the way of the kind of work I wanted to publish, I either changed the workflow or pulled more of the system into the repo so I could control it.

If you read the whole series, the takeaway I want to leave is that this portfolio is not just a gallery of finished projects. It is also a long-running exercise in building the system that can hold the work without flattening it.