Migrating to Pelican

I spend a lot of my time at the command line — working, writing code, exploring Python, and taking notes while I get my learn on (watching lectures, attending lectures, going to meetups, you name it). A few years ago, I began exploring the idea blogging using static site generators, starting with Octopress at work.

This one is built in Pelican. I write my post in Markdown, run a build sequence (in which the software renders complete HTML, CSS, and JavaScript from the markdown files based on template settings), and deploy it to my server. I don’t need to be concerned with database performance or security updates.

I’ve wanted to move away from WordPress for some time. It’s nice enough software and all, but it could be more secure. Besides, Pelican uses Python and Jinja, which I use at work. Blogging from the command-line is fun. I could probably install this whole blogging engine and even serve it from a Raspberry Pi if I wanted to. And, since my comments are in the hands of Disqus, I’m not going to have to deal with the spam factor.

There’s also this:

def another_cool_feature():
    return 'code examples with syntax coloring, too'

Here we go!