Reluctantly bucking the static trend

I recently redid my website, not that long after I redid my website, and not long before that I… redid my website.

I have been fully on board the static website train for a while, using it more and more at work, especially for smaller sites. Minimal computing is popular in Digital Humanities, for good reason. The main draw for me is in maintenance, especially for sites that are unlikely to be added to frequently, aren’t massive, and don’t need server side code to support special features.

So, I tried out several static site generators for my own site. I liked all of them! The first one I tried was Jekyll, which I was already familiar with from using for GitHub Pages, which we are using for Women Writers Recovery Hub editorial framework. I like a lot of things about Jekyll: I’m used to Ruby, so it felt comfortable (especially newer user versions of Jekyll), and I mostly liked the way it was set up. It felt better maintained at the time than Middleman, which I had also used for work.

I really liked working in Markdown, but found Jekyll a bit limiting in options, and I didn’t like some of the decisions it made for me. I tried Eleventy next, drawn to the extra minimal setup, active community, and I wanted to learn more about non frontend Javascript anyway. I enjoyed setting up Eleventy, and found the Markdown parsing to be very easy to customize, but once again ran into problems with other customization.

I found I just wasn’t updating my site very often, because the small amount of friction in needing to open a plain text editor and not being taken specifically to a writing environment was enough to slow me down. I also wanted to be able to create posts on my phone if I wanted, or start on my phone and edit on my computer. I was already working with markdown files in Obsidian and using syncthing to sync that to my computer, and wouldn’t it be great if I could just have an Obsidian vault that was my website? I could, of course, pay Obsidian to do that, but the customization options were, again, limited. I tried doing this in Eleventy and kept running into problems, so I found another static site generator written in TypeScript called Quartz which would take an Obsidian vault and create a static site. I really liked working with Quartz – I found it easy to alter and I liked the idea of the “digital garden” rather than a blog like format.

BUT… I still wasn’t updating my site. Creating posts in Obsidian was easy enough, but there was always a little bit of friction in adding images from my phone (where most of my images are), I still needed to log into my site to run the build command, and I found I kind of missed the date based format a blog provided. My RSS feed broke and I couldn’t easily figure out how to fix it. There were ways around all of this, of course, but I found myself wishing for an interface I could just log into and post.

So, after all of this I ended up back with WordPress, which is a snap to install with Installatron on my shared hosting through Reclaim Hosting (who I have been with years and years at this point). It’s not the BEST time to go back to WordPress, but I was looking for a site that I could potentially plug into the Fediverse and WordPress is the only shared hosting friendly CMS with a fediverse plugin (unfortunately I have not quite been able to make it function perfectly yet, so it is currently disabled).  I’m avoiding any Jetpack stuff this time around. I’ve also started with underscores for my theme, rather than going through the frustrating process of undoing others’ design decisions (though I’m not using many of the special features). I’ve installed a caching plugin to hopefully keep some of the speed benefits I had with a static site. Like I did the last time I abandoned my WordPress site, I plan to create a static version to keep links working when I change website architecture again, though this time I am making other decisions to hopefully more fully integrate the old and new sites when I do.

Lessons Learned

I’ve learned a few things about myself. While I love the “digital garden” format of website, I find it hard to apply to my own site. Adding things to a dated stream of posts, with categories, is a lower friction way for me to create than reconsidering each time how content fits into the overall website. The “traditional” blog fits well with how my brain and sense of organization work. I learned that when I am in writing/creating mode, I really do not want to deal with the technical details, so I get frustrated when the writing experience is interrupted with troubleshooting. I also learned I place a premium on convenience at the point of creation.

I do still have some ideas for some static websites, though. I think static site generators are terrific for building one off sites and experiments, and I hope to do more of that in the future rather than working it all in to one WordPress install.