Getting started with Pelican: A Python-based static site generator

Pelican is a great choice for Python users who want to self-host a simple website or blog.
294 readers like this.

If you want to create a custom website or blog, you have a lot of options. Many providers will host your website and do much of the work for you. (WordPress is an extremely popular option.) But you lose some flexibility by using a hosted solution. As a software developer, I prefer to manage my own server and keep more freedom in how my website operates.

However, it is a fair amount of work to manage a web server. Installing it and getting a simple application up to serve content is easy enough. But keeping on top of security patches and updates is very time-consuming. If you just want to serve static web pages, having a web server and a host of applications may be more effort than it's worth. Creating HTML pages by hand is also not a good option.

This is where a static site generator can come in. These applications use templates to create all the static pages you want and cross-link them with associated metadata. (e.g., showing all the pages with a common tag or keyword.) Static site generators help you create a site with a common look and feel using elements like navigation areas and a header and footer.

I have been using Python for years now. So, when I first started looking for something to generate static HTML pages, I wanted something written in Python. The main reason is that I often want to peek into the internals of how an application works, and using a language that I already know makes that easier. (If that isn't important to you or you don't use Python, there are some other great static site generators that use Ruby, JavaScript, and other languages.)

I decided to give Pelican a try. It is a commonly used static site generator written in Python. It directly supports reStructuredText and can support Markdown when the required package is installed. All the tasks are performed via command-line interface (CLI) tools, which makes it simple for anyone familiar with the command line. And its simple quickstart CLI tool makes creating a website extremely easy.

In this article, I'll explain how to install Pelican 4, add an article, and change the default theme. (Note: This was all developed on MacOS; it should work the same using any flavor of Unix/Linux, but I don't have a Windows host to test on.)

Installation and configuration

The first step is to create a virtualenv and install Pelican.

$ mkdir test-site
$ cd test-site
$ python3 -m venv venv
$ ./venv/bin/pip install --upgrade pip
Successfully installed pip-18.1
$ ./venv/bin/pip install pelican
Collecting pelican
Successfully installed MarkupSafe-1.1.0 blinker-1.4 docutils-0.14 feedgenerator-1.9 jinja2-2.10 pelican-4.0.1 pygments-2.3.1 python-dateutil-2.7.5 pytz-2018.7 six-1.12.0 unidecode-1.0.23

To keep things simple, I entered values for the title and author and replied N to URL prefix and article pagination. (For the rest of the questions, I used the default given.)

Pelican's quickstart CLI tool will create the basic layout and a few files to get you started. Run the pelican-quickstart command. To keep things simple, I entered values for the title and author and replied N to URL prefix and article pagination. It is very easy to change these settings in the configuration file later.

$ ./venv/bin/pelican-quickstart
Welcome to pelican-quickstart v4.0.1.

This script will help you create a new Pelican-based website.

Please answer the following questions so this script can generate the files needed by Pelican.

> Where do you want to create your new web site? [.]
> What will be the title of this web site? My Test Blog
> Who will be the author of this web site? Craig
> What will be the default language of this web site? [en]
> Do you want to specify a URL prefix? e.g., (Y/n) n
> Do you want to enable article pagination? (Y/n) n
> What is your time zone? [Europe/Paris]
> Do you want to generate a to automate generation and publishing? (Y/n)
> Do you want to upload your website using FTP? (y/N)
> Do you want to upload your website using SSH? (y/N)
> Do you want to upload your website using Dropbox? (y/N)
> Do you want to upload your website using S3? (y/N)
> Do you want to upload your website using Rackspace Cloud Files? (y/N)
> Do you want to upload your website using GitHub Pages? (y/N)
Done. Your new project is available at /Users/craig/tmp/pelican/test-site

All the files you need to get started are ready to go.

The quickstart defaults to the Europe/Paris time zone, so change that before proceeding. Open the file in your favorite text editor. Look for the TIMEZONE variable.

TIMEZONE = 'Europe/Paris'

Change it to UTC.


To update the social settings, look for the SOCIAL variable in

SOCIAL = (('You can add links in your config file', '#'),
          ('Another social link', '#'),)

I'll add a link to my Twitter account.

SOCIAL = (('Twitter (#craigs55)', ''),)

Notice that trailing comma—it's important. That comma helps Python recognize the variable is actually a set. Make sure you don't delete that comma.

Now you have the basics of a site. The quickstart created a Makefile with a number of targets. Giving the devserver target to make will start a development server on your machine so you can preview everything. The CLI commands used in the Makefile are assumed to be part of your PATH, so you need to activate the virtualenv first.

$ source ./venv/bin/activate
$ make devserver
pelican -lr /Users/craig/tmp/pelican/test-site/content o
/Users/craig/tmp/pelican/test-site/output -s /Users/craig/tmp/pelican/test-site/

-> Modified: theme, settings. regenerating...
WARNING: No valid files found in content for the active readers:
   | BaseReader (static)
   | HTMLReader (htm, html)
   | RstReader (rst)
Done: Processed 0 articles, 0 drafts, 0 pages, 0 hidden pages and 0 draft pages in 0.18 seconds.

Point your favorite browser to http://localhost:8000 to see your simple test blog.

Pelican test site 1

You can see the Twitter link on the right side and some links to Pelican, Python, and Jinja to the left of it. (Jinja is a great templating language that Pelican can use. You can learn more about it in Jinja's documentation.)

Adding content

Now that you have a basic site, add some content. First, add a file called welcome.rst to the site's content directory. In your favorite text editor, create a file with the following text:

$ pwd
$ cat content/welcome.rst

Welcome to my blog!

:date: 20181216 08:30
:tags: welcome
:category: Intro
:slug: welcome
:author: Craig
:summary: Welcome document

Welcome to my blog.
This is a short page just to show how to put up a static page.

The metadata lines—date, tags, etc.—are automatically parsed by Pelican.

After you write the file, the devserver should output something like this:

-> Modified: content. regenerating...
Done: Processed 1 article, 0 drafts, 0 pages, 0 hidden pages and 0 draft pages in 0.10 seconds.

Reload your test site in your browser to view the changes.

Pelican test site 2

The metadata (e.g., date and tags) were automatically added to the page. Also, Pelican automatically detected the intro category and added the section to the top navigation.

Change the theme

One of the nicest parts of working with popular, open source software like Pelican is that many users will make changes and contribute them back to the project. Many of the contributions are in the form of themes.

A site's theme sets colors, layout options, etc. It's really easy to try out new themes. You can preview many of them at Pelican Themes.

First, clone the GitHub repo:

$ cd ..
$ git clone --recursive
Cloning into 'pelicanthemes'...

Since I like the color blue, I'll try blueidea.

Edit and add the following line:

THEME = '/Users/craig/tmp/pelican/pelican-themes/blueidea/'

The devserver will regenerate your output. Reload the webpage in your browser to see the new theme.

Pelican test site 3

The theme controls many aspects of the layout. For example, in the default theme, you can see the category (Intro) with the meta tags next to the article. But that category is not displayed in the blueidea theme.

Other considerations

This was a pretty quick introduction to Pelican. There are a couple of important topics that I did not cover.

First, one reason I was hesitant to move to a static site was that it wouldn't allow discussions on the articles. Fortunately, there are some third-party providers that will host discussions for you. The one I am currently looking at is Disqus.

Next, everything above was done on my local machine. If I want others to view my site, I'll have to upload the pre-generated HTML files somewhere. If you look at the pelican-quickstart output, you will see options for using FTP, SSH, S3, and even GitHub Pages. Each option has its pros and cons. But, if I had to choose one, I would likely publish to GitHub Pages.

Pelican has many other features—I am still learning more about it every day. If you want to self-host a website or a blog with simple, static content and you want to use Python, Pelican is a great choice. It has an active user community that is fixing bugs, adding features, and creating new and interesting themes. Give it a try!

User profile image.
Currently, an SRE at Aurora. I have been at large companies and small ones. I have seen amazing growth (at LinkedIn and NetApp) and a couple completely fall apart. I am passionate about how SRE (and DevOps, in general) can change how online software is developed and managed.


./venv/bin/pelicanquickstart ----> ./venv/bin/pelican-quickstart

I am more interested in a LAN setup that would require a light-weight web server. Any suggestions?

If you are asking about just a web server (without discussing any kind of blogging software), then I use nginx. That is what all of my recent companies have used, so that is what I am most familiar with.

If you are looking for something Python-specific, then I use Flask. It's pretty lightweight. But, it's pretty minimal, which works for me. (FTR; one company I worked for a year or so ago was pretty heavily invested in Django. It worked well and had lots of bells and whistles. But, when I tried it for personal stuff, it was a bit much to bite off. Flask has much less "built in", but it was easy to get up and running.)

Hope that helps.

In reply to by ken

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.