Migrating my website to Pelican

2017-11-04 - Louis-Philippe Véronneau

After too much time lying to myself, telling myself things like "I'll just add this neat feature I want on my blog next week", I've finally made the big jump, ditched django and migrated my website to Pelican.

I'm going to the Cambridge Mini-Debconf at the end of the month for the Debconf Videoteam Autumn sprint and I've taken the task of making daily sprint reports for the team. That in return means I have to publish my blog on Planet Debian. My old website not having feeds made this a little hard and this perfect storm gave me the energy to make the migration happen.

Anyway, django was fun. Building a (crappy) custom blogging engine with it taught me some rough basics, but honestly I don't know why I ever thought it was a good idea.

Don't get me wrong: django is great and should definitely be used for large and complicated websites. My blog just ain't one.

Migrating to Pelican was pretty easy since it also uses Jinja2 templates and generates content from Mardown. The hardest part was actually bending it to replicate the weird and specific behavior I wanted it to have.

So yeah, woooo, I migrated to Pelican. Who cares, right? Well, if you are amongst the very, very few people who read the blog posts I mainly write for myself, you'll be please to know that:

  • Tags are now implemented
  • You can subscribe to a wide array of ATOM feeds to follow my blog

Here's a bonus picture of a Pelican from Wikimedia, just for the sake of it:

A pelican


websitedebiandebconf