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.
I started this repo because I wanted a place to publish projects. That was the whole brief. Built the first version of the portfolio, pushed past the starter-template stage, and turned an initial Zola site into the beginning of a custom publishing system.
Once I moved to Gatsby, the problem stopped being “how do I have a site?” and became “how do I structure a site that can actually hold the work I want to publish?” Built a content-driven portfolio model with tags, series, clusters, page-generation rules, and stronger TypeScript-checked structure.
At some point I realized that plain markdown was not visually or structurally distinct enough for the kind of work I wanted to publish. Expanded the site into a denser technical publishing tool with notebook embedding, richer article framing, and better support for project artifacts that did not fit clean blog-post shapes.
The least glamorous part of this repo is probably the most representative part. Recovered the site from toolchain drift by pinning dependencies, vendoring unstable pieces, and treating maintenance work as part of the product instead of background cleanup.