Switching The Jimternet From Wordpress to Pelican

I've just finished migrating The Jimternet from Wordpress to Pelican, a static blog generator written in Python. There are already plenty of posts extolling the virtures of Pelican and static blogs in general, so I'll simply share why the static blog paradigm makes sense for me.

For the uninitiated: dynamic Content Managemnt Systems such as Wordpress re-generate html each time a page is requested, (caching notwithstanding). The web server hosting the site in question does this by executing scripts, which in turn read content from a database backend.

This is a powerful paradigm which allows for almost infinite complexity. But by their very nature, blogs are relatively static websites. A blogger composes a post, publishes it and then nothing changes until the next post is published.

Recognising this, Static site generators such as Pelican produce a website composed entirely of html files. Content is authored in either Markdown or RST and the site's configuration is maintained in a single file. When a new piece of content is added, Pelican re-generates the entire site from scratch. The result is a directory of html files, ready to be uploaded to a web server for hosting, (those old enough to have created a website in the 1990's may feel a vague sense of deju-vu).

Continue Reading Comments