Will Ranjan-Churchill

My current posting workflow

I love Jekyll, but it's sometimes a pain when you just want to throw something online. Here's my over-engineered solution.

I chop and change my website almost more than I actually write on it. For giggles, I thought I'd share what my current website setup and posting workflow is.

This site uses Jekyll. I love it because I do almost all of my writing in Markdown, meanwhile the flat file nature of the site means its simple, fast, and I don't have to worry about logins etc.

The thing is, getting from Markdown to webpage isn't quite as easy as the casual poster might like (I've talked about this before). Depending on your particular flavour of setup, it usually involves either sending your files to GitHub pages, creating a version of your site on your computer and then uploading it to your web server, or running the whole thing on a server that allows Ruby (which Jekyll needs to run).

I don't like any of those options. GitHub pages is objectively the easiest of these but limits done of the things you can do (e.g. no Jekyll plugins). Meanwhile, paying for a Ruby-enabled web server just to run a flat file website seems insane. So for a while I've been opting for the "run it locally and then upload" option. But there's a couple of things that bug me about it. The main one is that I tend to chop and change the device I'm working on quite a bit. This means installing Jekyll and the whole site onto each device, and rules out using my phone for anything.

On top of that, I tend to do all my writing in Obsidian, so copying stuff out into VSCode to then run through Jekyll is an additional step that seems pointless.

But that gave me an idea. I already use Obsidian Sync to send my Vault to a private git repo on a Raspberry Pi. Could I make my own version of GitHub pages?

Turns out, I can.

So here's my current workflow:

Git Sync runs every few minutes and once the runner fires the build and send process takes maybe 3 minutes, even on an older model RPi. Between the repo, the site build, and the sFTPing, I'm making the little board work. But it's pretty much the only thing it does, so I don't feel too bad for it. The time between putting the file in the publish folder and the live site showing the changes is never more than about 5 minutes.

Is the process over engineered? Of course it is. There are a dozen ways to easily setup a blogging website, and if you care that much about writing offline then just write into an offline doc and copy/paste when you're back online. That said, it does make it super easy to write a post from any of my devices, regardless of whether I'm online or offline. Case in point, I'm writing this on my phone on a flight right now. When I'm done, I'll pop it in the publish folder and forget about it. When I land and take my phone off airplane mode, everything will fire off in the background. EDIT: turns out I forgot that Obsidian on mobile doesn't sync in the background (because why would it?), so this isn't technically true. But all I had to do was open the app and wait a few seconds, so not bad.

Would I recommend the setup to anyone else? Almost certainly not. I do it this way because I have a borderline unhealthy attachment to Obsidian, a Raspberry Pi that was collecting dust, and a real need to tinker with things.

Is this what my site setup will look like for the rest of time? Nah - I'll get bored before the end of the year and probably move the whole thing to something new (bookies' favourite at the moment is Pure Blog). But for now it's fun, and scratches a nerdy dev itch.

markdown, obsidian, internet


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
Calling AI a technology is wrong - or at least incomplete

Next post ➡
I'm worried we're stopping kids from learning tech