Today, I was idly thinking about the kind of thing I used to spend ages doing: designing loads of different websites, rather than just Dirty Feed. Among them were stuff like Ganymede & Titan, Gypsy Creams, and Noise to Signal, all at one point using the CMS Drupal.
None of those sites still use Drupal, however. The spectre of those sites breaking whenever I tried to update the backend still haunts me to this day. The incompatibility and general unpleasantness was absolutely rife. In the end, Ganymede & Titan and Gypsy Creams were converted to WordPress, and as Noise to Signal was changing from an ongoing site to an archive, I just made it all static HTML pages. Has Drupal improved its upgrade path since then? I haven’t the foggiest. I was burnt multiple times, and was warned off it for good.
Anyway, in an odd bit of coincidence1, today I also spotted designer Greg Storey posting about his current CMS woes:
“In fourteen days the CMS I use to run this site, Forestry, will be shut down for good and until I migrate to another system this site will be frozen in time. Don’t stop the presses here, the world will continue to rotate but this situation sucks. It’s like when a commercial or government entity makes a mistake that you have to now find time to fix. While software as a service makes a lot of sense, someone else’s problems are now my own. And I have to be honest, I’m not thrilled by my options because they either tie me to the same situation or they require time and money to fix.”
This must be especially annoying, as Greg’s site was only rebuilt and relaunched in 2019. In less than four years, the site has gone from relaunched, to stuck in stasis.
* * *
Ever since I launched Dirty Feed in 2010, it has used self-hosted WordPress. No Drupal, no Movable Type, and certainly none of the more modern or interesting solutions. Do I love it?
Not really. I like designing my own themes from scratch, but this is now really quite complicated, and has only got worse over the years.2 And it’s not the only thing which is complicated: the whole thing is clearly over-powered for what I need here. I only use a fraction of the features WordPress offers. Of course, everybody needs a different fraction of those features, and that’s where the problem always starts. We’ll find a proper solution to that one in the year 2942.
But WordPress has done two things for me. Firstly, it’s remained remarkably free of upgrade woes; there were a couple of wrinkles with comments and videos a few years back, but nothing like the bad old days of Drupal, and certainly nothing which has stopped me making new posts on here And secondly, it’s got the fuck out of my way, and let me concentrate on the thing I want to do most these days: writing.
Monocultures are bad, and everybody using WordPress would be a terrible thing. I fully admit that I’ve taken the easy way out. But sometimes, you have to pick your battles. My experience with Drupal taught me one thing: I needed software which wouldn’t keep kicking me in the balls.
WordPress isn’t cool. For most needs, it’s bloated. There are far more elegant solutions out there. But upgrades aren’t a hassle, and it ain’t going anywhere.
Sometimes, if all you want to do is write, those are the only things which really matter.