(In)coherent grumbles.

Moving my blog to Soupault

Last update:
Reading time: less than a minute

Moving my blog to Soupault

I feel like all the people I follow have a post like this, so it only makes sense to have one for me as well. Is it actually useful? No, not really I suppose. Does it give me an excuse to write a small thing? Absolutely.

The before times

Originally, what I did to get thoughts out into the wild was to write a markdown document, and then run pandoc to generate the html files that are served using github pages. I had an index.html in the root of the repo that linked to all of the other html files and it worked just fine. Good ol' regular html, the stuff of yore.

Nowadays

I write regular markdown files, and they're converted to html files in a build directory using Soupault with Github Actions. Github Pages then serves the contents of the build director for y'all to see. Still good ol' regular html, but with a different path to the same destination.

I've updated the structure of my repo to match what the soupault blog blueprint expects, makes it much easier to generate.

Was the switch worth the effort?

It's still pretty early on, but...

Should you switch?

Depends (but really, probably not).

Do you already have your setup working as you like it?

Why Soupault instead of ?

Saw it on Hacker News and thought it seemed pretty neat. I knew that I wanted to update my process and got nerd sniped :) I think it worked out pretty well in the end.