In attempting to choose a backend for this site, I experienced a kind of mental paralysis induced by too many options called The Paradox of Choice after a famous book by that title. The phenomenon is also called overchoice, a great word coined in Future Shock (another book I should read).

I considered using Drupal, Wordpress and many of the 1200+ alternatives, trying to find something light, flexible and efficient. After considerable effort, I had narrowed it down to a handful of minimalist CMS projects (e.g. Textpattern, Pico, Monstra), when I stumbled on a new idea.

At the bottom of GitHub Pages I noticed the text:

Using Jekyll, you can blog using beautiful Markdown syntax, and without having to deal with any databases.

Um, yes please. As it turns out, Jekyll is considered a static site generator, rather than a CMS, because the latter implies dynamic page generation on the server side (although I’m not entirely convinced of the distinction).

With Jekyll, despite the existence of dozens of alternatives, the burden of overchoice is relieved by the fact that the switching cost is extremely low. You can feed it simple Markdown, which is very portable. Meanwhile, Jekyll is the definition of minimal, weighing a slender 3,363 lines of code (as counted by my sloccount).

So, this site, which is clearly not a blog, is going to be Jekyll-powered and stored on Github.