Two AIs, One Migration

Sep 16, 2026 · Building

The idea for this wasn't mine — it was Claude's. In a planning session it said the highest-leverage change left was moving the site to a static site generator: I'd already tripped over the nav-sync bug twice, and every new page made keeping language versions in sync by hand harder. A shared template would end it permanently.

opencode and I did the work. The main steps:

Install: npm install --save-dev @11ty/eleventy; configure .eleventy.js to read src/ and output _site/.
Templates: one shared layout per language in src/_includes/ for the nav and footer; each page becomes a template with a permalink that keeps the old .html URLs.
Blog: posts are Markdown in src/posts/ with a date and category; the index builds itself from the post collection.
Build: npm run build writes everything to _site/; npm run serve live-previews at localhost:8080.
Deploy: wrangler.toml now serves ./_site; the generated _site/ is committed, so git push still ships the site.

What didn't change matters more. The pages the browser loads are still plain HTML — same CSS, same JavaScript, same URLs. Eleventy is a build tool, not a runtime framework, so the "no frameworks" spirit survives. The difference is pages get assembled instead of pasted.

The honest footnote: this site is written by opencode and steered by me — and the migration idea came from Claude. Three parties, one tiny website. It's true, so the site says so.