Blogging with Pelican
Blogging with Pelican
I switched to Pelican from Wordpress so that I could design the blog I wanted. Creating a blog in Pelican is a great way to learn HTML, CSS, Jinja templates and Git.

When I began blogging in 2016, I became more aware of how blogs are designed. Many of my favorting blogs had simple designs which made it easier to focus on the content, and they loaded really fast. (E.g. and CuriousGnu). I wanted this for my blog, too. I'd used Wordpress to build and publish my blog which was a great way to begin, but I felt I was compromising on its design and functionality. I wanted to have control over my blog's features.

This led me to static sites which contain only fixed content and are faster to load and easier to design than one built using a dynamic blogging platform such as Wordpress. Because I was already familiar with Python I chose Pelican rather than another static site generator such as Jekyll.

There are plenty of sites to tell you how to start blogging in Pelican, so here I will focus on my experience after the initial set-up. When I was learning how to begin, I found Amy Hanlons blog particularly useful and clear.

The learning curve

… was longer than I expected. Since setting out to switch from Wordpress to Pelican, I've taught myself enough of the following tools to hack this site together. I'm really happy about this because these tools could be used in future projects too.


I find HTML quirky but intuitive. Tags make sense, comments are laborious and learning by google is relatively quick. Whatever it is I'm trying to do (like add a link to jump back to the top of the page) someone will have posted the answer somewhere.


Writing CSS feels a lot more concise that HTML but it also felt impossible to learn without taking a step back and reading an introductory course. Usually I learn by hacking new phrases together from existing examples so it was frustrating to go backwards before progressing. There was a lightbulb moment when I realised CSS Selectors were a thing, and realising CSS files get called in the header (usually) of an HTML file…

I ended up using a trial subscription to Thinkfuls Front-end developer course, which is pretty good at explaining how CSS is structured and how to arrange content on a page. If I still had access, I'd be completing the second half of the course :)

Jinja templates

Jinja is a tool written in Python to create HTML pages. It doesn't look intuitive to me, but I've been able to get enough done by copy-pasting similar snippets from other parts of the theme I started with (Thanks Molivier!) to make the changes I wanted. I'd like to learn more as it seems really powerful.


To build a website using Pelican, you need to run commands from the terminal. There are various commands but I found myself using only a few regularly. "Pelican-quickstart" will generate a project skeleton to get you started. "make devserver" will initialise a local server and generate output files so that I can view changes locally before uploading (its opposite is "make stopserver"). Finally "pelican content -s" generates the html and css for remote hosting. Some of the plugins I use such as "Assets" which minifies the CSS only work when is called, which confused me initially as I didn't think it was working when I was only using "make devserver".


This really challenged me, and I still don't feel like I know what I'm doing. Git is far more powerful than I need it to be, when all I want to do is undo some erroneous edits and upload a new version of the site to Github.

I can stage and commit files, I can create local and remote repo's from the command line. I can change a remote's URL, reset a repo and force a push or a pull. That's all. I haven't tried to merge or to create a test branch, and if some part of the process goes wrong it usually takes hours to make it right again.

This is one tool for which the awesome SO and Google cannot magic up the exact right answer immediatly, unfortunately.

For example, there is still an output folder in the source repo that is… mysterious to me. Its not the real output, its a version frozen in time from a few weeks ago, and it has an "@" in its name. I don't know how it got there. It was created one afternoon in a blur of frustrated google queries and copy/paste/hope terminal commands.

I find git's commands the least intuitive of all the tools I use, with its preceeding single dashes and double dashes, and random words thrown into the middle of otherwise reasonable commands.

But Git is ubiquitous and Github is awesome, so I will learn it.

Github pages with an external URL

You'll need to add a file called CNAME to the repo containing the output. CNAME should contain the address of your site in lowercase. Simple.

You'll also need to update the DNS records of your domain name to point the name at Github's servers. For Github, you need two "A Records" with host type "@" and values "" and "" respectively. You also need a CNAME record with host type "www" and the value equal to "". It took about 12 hours for the changes to propagate, and during that time I had variable success loading the site.


One thing I didn't want when moving away from Wordpress was a site bloated with features that didn't make the content easier to read. However I found I still needed a few plugins to optimise my site and provide some basic functionality that doesn't come with the vanilla Pelican.

iPython notebooks

Super useful, as all I need to do to publish a notebook as a webpage is copy the .ipynb file into the context directory and add a sidecar .ipynb-meta file with standard meta data. This functionality is one of the main reasons why Pelican is popular with data bloggers. (Though Nikola is another option).


At the end of a post there should be a link to the previous and next blog posts - I was surprised this wasn't included as standard. After putting the plugin in the plugins folder and updating, you need to copy a couple of jinja snippets into a template, and maybe add some css to make the links look nice.

Optimise images

Make those images as small as possible to help make the site as fast as possible. Add the plugin, update, and thats all.


Before I started working with Pelican, minifying css and JavaScript would have been too advanced. But once Pingdom and Google Pagespeed started criticising me for my multiple .css files, I accepted the challenge.


I'm super happy wth the websites design and speed. It's designed the way I want it, and I've learnt a ton of useful stuff along the way.

Update: My second post about blogging in Pelican is here.