← Publishing a web project with MSBuild (with multiple configurations) | Excel found unreadable content (when exporting a Reporting Services report) →

Hello, Jekyll!

| tags: jekyll, blogofile, markdown

I migrated this site again…this time to Jekyll.
Why again? When I migrated from WordPress to Blogofile in the beginning of 2013, I evaluated other static site generators (Octopress and Pelican) as well, before settling on Blogofile. I knew at the time that Jekyll existed and that Octopress is based on it, but I didn’t take a closer look.

After reading a few recent posts by other people who migrated to Jekyll, I became interested in Jekyll again. Originally I just started to convert my site to Jekyll to see how it works and how it’s different/similar to Blogofile, but in the end I converted the complete site and decided to stay with Jekyll.

There’s no real reason why…I guess it’s just because Jekyll is all the rage now :-)
Apart from the fact that Jekyll is slightly more popular (starred on GitHub 13,476 vs. 295 times, as of now), Jekyll and Blogofile are largely the same.

Some things are easier to do in Blogofile, some are easier to do in Jekyll:

Oh, and of course I needed to re-build my previous solution to display Markdown files from my Bitbucket projects (again).
Here’s the Jekyll code to generate the PHP pages.

Concerning hosting:
The default Jekyll setup these days seems to be using GitHub Pages, but my site is still hosted on my own webspace (I’m paying for it anyway, and I prefer to use Mercurial, not Git).


← Publishing a web project with MSBuild (with multiple configurations) | Excel found unreadable content (when exporting a Reporting Services report) →