26W22. Swapping the engines mid-flight

I don’t know why it suddenly dawned on me, but i’m not sure why i chose to build Z1NZ0L1N and Architypes with a full-fat CMS. I’d been using Pelican and Hugo for almost fifteen years by that point, so i’ll chalk it up to some sort of static site generator fatigue. It took me more than a year to remember why i abandoned CMSes in the first place: they have pretty much every feature that i need… and a lot i don’t. Ghost isn’t a bad CMS, but i don’t want to turn my audience “into a business”. I don’t need integrated analytics, a newsletter engine, a clunky attempt at federation, and reminders to adopt “content distribution tactics” to get more people to discover my work and increase engagement. If i’m using a CMS, though, i’d like to be able to manage my uploads in a media library and to organize my content with more than a single taxonomy. I guess those features aren’t shiny enough for the tech bros who Ghost is trying to lure away from Substack and Medium. Going back to Hugo means…