Key takeaway: For a Python shop that wants its blog on the same toolchain as everything else, Pelican is the sane default. It is mature rather than exciting, and that is the point: Jinja2 templates, Markdown or reStructuredText in, HTML out. Anyone without a Python reason should look at Eleventy or Hugo first.
Quick facts
- LanguagePython
- CategoryPython
- LicenseAGPL-3.0
- Created2010
- GitHub stars12.7k
- Statusmature
Templating: Jinja2 Markdown reStructuredText
What it is
Pelican is the most-used Python SSG. Blog-shaped, Jinja2 templates, Markdown + reStructuredText support. Mature and stable; popular with the Python developer community.
Best for
- Python-shop blogs
- Documentation paired with reStructuredText (Sphinx-adjacent workflows)
- Teams that prefer keeping the toolchain in Python
When not to pick it
For non-Python teams, the JS-based options (Astro, Eleventy) will offer a bigger ecosystem and more recent feature work.
My take
Pelican is fine for Python teams writing blogs. Outside that audience, the cost of a Python toolchain in a JS-dominated ecosystem is real.
Jinja2, Markdown, and the reStructuredText option
Pelican's shape is immediately familiar to anyone who has used Jekyll: content files with metadata at the top, Jinja2 templates, a theme directory, a settings file. The difference that matters is native reStructuredText support alongside Markdown, which makes it the easy pick when your existing documentation and docstrings are already reST and you want one markup language across the project. Plugins cover the usual needs, feeds, sitemaps, related posts, and because everything is plain Python you can write your own in an afternoon rather than learning a plugin API in a language you do not use. The theme selection is smaller and visually older than the JavaScript ecosystem offers, so expect to build or heavily modify a theme rather than picking one off the shelf. Build times are fine at blog scale and unremarkable on large catalogues.
The AGPL licence and what it means for a build tool
Pelican is AGPL licensed, which is unusual among static site generators and worth checking against your company's policy before it becomes an argument in a review. In practice it is a build-time tool: it runs on your machine or in CI and produces plain HTML, and the HTML you publish is your content rather than a derivative of the generator. The AGPL's network clause is aimed at running modified software as a service, which is not what happens when you upload a folder of files. That said, plenty of legal teams operate a blanket ban on AGPL dependencies and will not engage with the distinction. If yours is one of them, Eleventy, Hugo, and MkDocs are permissively licensed and cover the same ground without the conversation.
Frequently asked questions
Is Pelican still maintained?
Yes, but treat it as mature rather than fast-moving. Releases arrive at a steady, unhurried pace and the focus is stability over new capability, which is appropriate for a tool whose job has not changed much. That is a feature for a blog you want to leave alone for years, and a drawback if you expect the kind of feature velocity Astro or Eleventy show.
Pelican or MkDocs?
MkDocs if you are building documentation, particularly with the Material theme, which gives you search, a structured sidebar, and the usual documentation conventions without configuration. Pelican if you are building a blog or a general content site, where MkDocs's documentation opinions get in the way. Both keep you in a pure Python toolchain, so the choice is about the shape of the content.
Does Pelican support reStructuredText?
Yes, natively, alongside Markdown, and you can mix both in the same site. That is the main reason to pick it over a JavaScript generator: if your project's docstrings, README, and existing documentation are already reST, you avoid maintaining two markup languages. Markdown support is equally first-class if you would rather not touch reST at all.
Links
Similar tools you should also consider
If Pelican is your pick, the next conversation is short
The 30-min call is where your project gets a real architecture, an SEO transport plan, and a price range you can take to your team. Describe your site, your timeline, your existing content. I tell you whether Pelican is genuinely the right call for you, and what the build actually looks like.