Moving to Jekyll

February 23, 2012 · ~200 words (1 min)
This post was written more than five years ago. I may still stand by it, but I may not. I try to grow as a person over time, and that inevitably means some of the stuff I wrote or thought before is embarrassing now, just like the things I write and think now will hopefully embarrass me in the future. I try to leave that old content up to preserve links and not pretend it didn’t happen, but that doesn’t mean I still endorse it. If you’re curious whether I still stand by this post, the best way to find out is to just ask me.
“You have your work and nothing more.”

—Jekyll & Hyde, the Musical

I’m considering moving my personal site over to Github pages to be powered by Jekyll. I like the capability to write my posts in Markdown and the free, reliable hosting that Github provides. I like the flexibility of the templating engine. Most of the restrictions and limitations of Jekyll are things that I won’t miss, anyways.

The fact that categories and tags aren’t as useful hurts. The insistence upon including dates in the filenames hurts. But Jekyll has so many features I like, I can’t see trading all of those for categories, posts, and filenames. I don’t know, it just seems like the pros far outweigh the cons.

This does mean, of course, that I have to make my own template. That’s the primary point of this post: testing it. I’m not a designer, but hopefully I didn’t embarrass myself too badly with this attempt. I wanted something green.