Will Ranjan-Churchill

4 reasons I'm back on WordPress

About four years ago, I spoke with great pride about moving my site from WordPress to Jekyll. I wanted something fast, easy to update, and that didn't require a whole lot from me.

Well, I'm back on WordPress now. Jekyll is fantastic, but here's 4 reasons I'm glad I changed back.

Jekyll wasn't as easy to post as I wanted it to be

When I first moved over, my setup was a little different. I posted infrequently, and when I did, it was a considered and dedicated process of sitting in front of my laptop and Hemmingwaying my way through the drafts.

In a setup like that, where I have one device that I always write on, and one method that I always use, a tool like Jekyll makes sense.

But I've recently changed how I read, which in turn has changed how I write. For one thing, I might take me a couple of days to write a post, which means that I'll be doing it over multiple devices, and I might want to finish and post from any of those devices. In this case, Jekyll presented some roadblocks. I procrastinate with writing at the best of times, so I need the process to be as frictionless as possible.

There are fixes and workarounds to this, of course. But when it gets to the point where your solution is more workaround than it is original platform, maybe it's time to rethink.

Besides…

Gutenberg is fantastic

Gutenberg - the wittly named built-in WordPress editor - has come on leaps and bounds in the last few updates. It's go so advanced that I'm actually working with a client at the moment to migrate them from a professional theme builder plugin, to Gutenberg. Their end-users will have the exact same end-user, but faster, and the client will be able to manage their website without the overheads of another plugin.

In fact, for my own site, I had switched back to WordPress expecting to build my themes from code. Yes, because I'm a nerd. But also because I like the look of my site, I had the theme files already in Jekyll, and it wouldn't have been too difficult to edit them for WordPress. In the end though, I didn't bother. I built all each page from scratch in Gutenberg. All in an afternoon. It was that easy.

To be clear, there are use cases where you would want a theme builder. But, as an untested-but-educated-guess, I suspect that well over half the people using one could seriously consider switching to the baked-in version.

I can still write in Markdown

One of the big reasons I moved to Jekyll was actually nothing to do with Jekyll. It was because I had started writing everything in Markdown - a syntax that makes it really simple to write in a structured manner without much thought. Markdown was the driver, and Jekyll was the logical way to turn those Markdown files into a website.

But WordPress handles Markdown perfectly well. Whether you're copy/pasting from a Markdown file into the editor, or you're syncing from your writing tool (Obsidian) to your publishing tool (WordPress) you don't need to worry about what the post will look like.

Some things are just easier with an actual interface

Markdown is great for a lot of things - including adding 95% of the styling you want to your text. Sometimes though, having an editor makes things so much easier.

Images are probably the thing that was the most "extra work" on Jekyll. With WordPress, I add it straight to where I want it (most often as the header image to the post) and the site will do the upload, compress the file, and make sure it's in the right place. Each of those steps was a manual process before. It wasn't arduous at all, but again, I'm very good at procrastinating on blogs.

So what does my writing process look like now?

Typically, something like this:

  1. Read something interesting, and decide I want to opine. This will usually happen in Omnivore, and maybe I'll have taken some notes within the platform.

  2. Often now, I'll actually dictate the first draft of my posts, rather than write them. I do this on my phone while I'm walking the dog, and copy/paste the automated transcript straight into Obsidian to carry on editing. Either way, Obsidian is where I engage the keyboard part of the process. If I've take notes in Omnivore, I'll pull them from a synced folder in Obsidian. Otherwise I'll just start writing.

  3. Depending on the topic, it might take me a couple of days to write the post. Obsidian syncs across all my devices, so I can pick it up and write anytime on any device.

  4. When I'm 90% happy with the post, I have a button in Obsidian that sends it to WordPress, as an unpublished draft.

  5. Opening up WordPress (again, from any device), I can make final edits - including stylistic things like adding images, or pullquotes. I'll also add in the metadata bits, like the category and tags, and the excerpt.

  6. I'll hit publish, and I'm done!

I will miss Jekyll, but it was the right move

I still love Jekyll, and it will always be a tool I consider when approaching new web-based projects. It's fast, very customisable, and of course Free and Open Source. And, as I alluded to right at the top, if there was something you wanted Jekyll to do, there was almost certainly a way to make it work.

As a nice little cherry on top, using a free GitHub account, and the free Jekyll software, you can run a great looking site for free. All you have to pay for, if you want it, is a custom domain name. Apart from that, it is (and I don't know if I mentioned this), free.

Beyond all that, it's undeniable that the WordPress site is slower to run. From an actual perfect PageSpeed insights score more or less out of the box, to currently sitting in the low 90s for desktop and mid 60s for mobile, there's definitely more work I need to do to this WordPress site before I'm happy.

On the flipside, I switched the site over last weekend, and I've already posted 3 new things. I already had a hosting provider - of course I did, I'm a web dev - but like Jekyll you can host a WordPress website site from as little as £0 on their servers. Or get your own for a few pounds a month if you want better customisation. There's a very good reason it's the world's most popular content management system.

I'm glad I went through my Jekyll phase. And I've no doubt I'll go back to it for something at some point.

But I'm also glad to be back on WordPress.

web development, wordpress


Want to chat about anything in this post? I'd love to hear from you!

Feel free to drop me an email

Or find me on Mastodon



⬅ Previous post
RSS: Why I think it's overdue a comeback

Next post ➡
No one is bad at tech