Blog Framework Overload

The current situation of the blogging frameworks is quite interesting, everyone seems to pop up with their own blog framework that does “something better” but then forgoes everything else and just focuses on that one “something better” feature, while neglecting anything and anyone else, which pretty much summarises the situation.

And while some frameworks do have quite useful things, there are times when you just want to write, press a button or two and have it show up somewhere on the internet.

It shouldn’t be stressful, full of problems and tinkering to get something to work the way it’s supposed to or the way someone thinks it should but it does something completely else because nothing is documented.

And so, a long long time ago, I went on a spree to try out as many blogging engines as I could. Some of them I tried out of pure interest, some of them had really nice features and some of them I tried because they were written either in languages I wanted to peruse or just a language I was comfortable with.

Wordpress, Ghost, Medium, Jekyll, Hugo, Hexo, Pelican, Octopress, Nikola and 300 other ones.

All in all, it came down to the same thing, you either miss a feature or two, and then you try to work around it or get it implemented and in the end, zero content and lots of frustration while getting there.

So after trying out almost all the blogging frameworks under the sun, I’ve moved to a minimalistic approach, with very little done by the blog itself and instead focusing on just the text.

In the end, I ended up settling on Hugo. It’s a simple, fast and it doesn’t come with a lot of cruft that can go wrong. All it takes is one binary file that does “everything” and you don’t need to make sure python reqs or node packages are installed. Zero frustration and lots of support for all sorts of input formats.