Shipping this blog: a few bumps along the way

This site went from an empty folder to live on blog.dimboo.net in an afternoon, but not without a few surprises — worth writing down before I forget them.

Plugin ecosystems move fast. By the time I actually installed dependencies, @11ty/eleventy-plugin-rss had gone ESM-only, which meant switching the config file from eleventy.config.js to eleventy.config.mjs and updating a couple of filter names that had been renamed upstream (rssLastUpdatedDate → getNewestCollectionItemDate | dateToRfc3339). Small fix, but a good reminder that a plan written even a few weeks earlier can drift out of date.

Cloudflare Pages deploys changed too. wrangler pages deploy no longer auto-creates the project on first run — you now need wrangler pages project create first, and a stray delegation to the newer unified Workers deploy path meant the very first attempt needed a --force flag to land on classic Pages. One-time hiccup; every deploy since has been a plain npm run deploy.

Domains don’t have to be all-or-nothing. dimboo.net was already doing a job elsewhere, so rather than fight over the apex domain, this blog just lives on blog.dimboo.net — a separate subdomain, attached as its own custom domain in Cloudflare Pages, without touching anything else on the root.

None of this was hard, exactly, just the usual cost of gluing together several fast-moving tools. Onward to actually writing about things other than the blog itself.