Workflow

Every AI coding session has the same quiet problem: when it ends, everything it learned ends with it. Close the window, and the agent that just spent an hour discovering exactly why your build was broken knows nothing about it tomorrow. You either re-explain everything from scratch, or you re-discover the same bug the hard way, again. This workspace runs two small tools specifically to stop that from happening.

If the only website tooling you've used is something like WordPress, Wix, or Squarespace — log in, click into an editor, hit publish — the idea of a "static site generator" can sound like a step backward. No login screen, no dashboard, no database. This site runs on one (Zola), and the tradeoffs are real in both directions, so here's the honest version rather than the sales pitch.

"AI-assisted" gets attached to everything right now, and it rarely means anything specific — it can mean "I asked a chatbot for a paragraph" or "an agent has been running unsupervised in production for a month." This entire blog network is genuinely AI-assisted, in a specific and describable way, so rather than talk about it abstractly, here's what that actually looked like on one real piece of work: getting the old after-dark Zola theme working again.

This entire blog network — the one you're reading right now — is built by working alongside an AI agent (Claude Code) on a home server, and it's the first real post to go out of that setup. Before writing about anything else, it felt right to write about the plumbing that makes the rest possible, because it's a pattern I think more people doing AI-assisted work should know about: two git remotes, not one.