The Death of Wordpress
After switching to WordPress almost 17 years ago, I’m done. Out. Finished.
In 2009, WordPress was The Thing. Prior to that, I had a homebrewed static site generator, more or less. It generated the index pages and slapped a header/footer on each generated page. Although I used various iterations of this for a dozen years, it had major shortcoming. I had to mostly edit posts by hand; images were a major pain; and the look and feel of the thing was not great. I also had to be in front of my laptop at home to edit a post.
I think I’d already been using WordPress for my music review blog (which died quickly, don’t ask) and after a big painful import process that involved too much use of the sed program and the ugliest shell script imaginable, I got everything into a self-hosted WordPress install.
WordPress had its advantages. Themes were great. It looked modern. I could easily log in from work or my phone or anywhere else and peck out a post. Things like comments were already included. And when I had a multi-person blog for the old publishing company, it wasn’t too terrible to set up other people to also edit things.
WordPress also had many fatal flaws. First of all, it was basically a vector for every possible Russian hacker imaginable, who were constantly on a global hunt to crack every WordPress site they could and turn it into a boner pill ad. This happened a few times on the old PL site, and luckily not at Rumored. You were also at the whim of the WP developers for updates and changes. When they switched to a more WYSIWYG editor with “blocks” in it, I almost jumped ship, until I found a way to turn back on the legacy editor.
I think the biggest pain in the ass was the perception that you could do anything with WordPress and it had a rich ecosystem. But any time I wanted to switch themes, I found most free themes were garbage, years old and unmaintained. Paid themes, sure. But I’m not paying thousands of dollars for a personal blog only three people read. Also there was this plugin architecture, and you’re supposed to be able to totally customize your site, but once again the freemium mode was a curse, and if you added more than a couple plugins, your site would slow to a crawl.
Another big thing was that I had all my posts in a screwy database format, and any thoughts about exporting them to another format to make a book or another site involved a graduate-level computer science project, or a plugin from someone in Yugoslavia that simply did not work.
So, done.
I’ve been doing the Markdown thing for a decade at work, writing with little symbols for italics and bold and headings, then using a static site generator to convert all of that into HTML and pour in templates and indexes and such. So I’ve thought about switching to a SSG for a long time. But the longer I waited, the worse this proposition got. I think there are about 1500 posts here, and 1.25 million words. So it’s not an easy lift.
I originally started using Jekyll at work in 2015, which suffers from the same WordPress freemium problem for themes and such, and definitely does not work well at that scale. Hugo is a bit better, but I never got it to look great. I use Gatsby for my other blog and that’s okay, but I kept sleeping on this for a while.
Anyway, I eventually thought about Astro, and that seemed to tick most of the boxes. I got a download of the WordPress export of this site, then broke it up into Markdown with a script that actually worked. After a quick setup and maybe two days of messing around, I got everything pretty much running here.
Another change is that I moved my hosting from AWS Lightsail to Vercel. And the actual files here live in GitHub. So Vercel watches the branches there and automatically does the builds and deployment. Easy stuff, and it wasn’t hard to get that running at all.
There are probably a lot of little things I need to fix here, broken links and style problems and such. There aren’t comments, and maybe I will add them back. (Or maybe not.) I need to spend some time on this, but I also need to say “done” and leave it alone.
The one disadvantage to this whole system: I’m now editing and publishing in the same tools I use at work: writing in VSC, testing in the command line, pushing changes with GitHub. Leaving work and then trying to be mindful and write, but sitting in the same exact programs is going to take some getting used to. Maybe I’ll write in something else, then paste it in here.
Other news is that I got another draft of Atmospheres 2 done, and I hope this is the second-to-last one. After I left it ferment for a week or so, I’ll start a heavy edit pass and hopefully get that done soon.


