Now it came time to figure out the technology to use for my blog. I put on my BA (Business Analyst) hat and figure out what I wanted exactly. So I had to figure out my requirements and choose the most suitable technology to meet them.

So my main need was the blog is easy to backup. This was a direct response to having a fairly outdated backup of my previous blog when I deleted it. Although this requirement seems straight forward, it also must be able to make sure I don’t have to constantly worry about my backups.

Another requirement that I had was that I wanted something that I could quickly and easy write posts. I don’t want to be spending too much time messing around with HTML. I just want to be able to quickly write a post and publish.

As with many software engineers I also wanted something that has an *awesome* factor to it. This means that I can make changes to it but generally it has high standing in the community.

Finally I wanted something that is quite low maintenance. I work fulltime and have other responsibilities, I don’t want to make a second job fixing up my blog, rebooting the server, etc. Just keep it simple and low touch.

So to summarize these requirements in agile stories:

  • As a blogger I want a blogging framework which is easy to back so that I don’t have to think about backing up
  • As a writer I want a blogging framework which is quick and easy to use so that I can easily write blog posts
  • As a software engineer I want a blogging framework which has an tech *awesome* factor so that I can show off
  • As a blogger I want a blogging framework which is low maintenance so that I don’t have to spend too much time making sure it is working

So I quickly ruled WordPress out of the equation due to the experiences I had previously and it not meeting my current requirements. I even had a look at an up and coming WordPress competitor Ghost but despite its features I turned away from it. The idea of writing my own blogging platform was definitely out of the question. But I did want to do my own hosting, so LinkedIn Posts and Medium was out of the picture. So as I looked, I settled on Jekyll.

So as I looked, I settled on Jekyll

Jekyll can be easily hosted on Github Pages, which met the easy to backup and low maintenance requirements. Unfortunently it did not quite meet the quick and easy to use requirement due to the use of Markdown. However coupled with a good Markdown editor like Mou, that problem can be mitigated. Lastly Jekyll definitely has a somewhat awesome tech factor.

I did also look at Octopress as a potential alternative to vanilla Jekyll however I decided to not use it. This was due to the lack of activity on the Github repository and the small community. In the future I might relook at using it, particularly for its plugins.

So there we have it, I opted to use Jekyll as the blogging platform for the reincarnation of my blog. Instead of directly looking at the shininess factor of the technology, I decided to take a structured approach in my selection.

So my next post is where I sum it all up!