Nikola: a Python static site generator for blogs with tags, feeds and galleries
A static website and blog generator
At a glance
- What is it?
- Nikola turns reStructuredText, Markdown and other source formats into a static website, using doit for builds and a plugin system for everything else. It is a reasonable fit for Python developers who want a blog engine they can read end to end, and a poor fit for anyone expecting a large hosted ecosystem.
- Who is it for?
- Adopt Nikola if you write in reStructuredText or Markdown, want tags, feeds, archives and galleries without a database, and are comfortable reading Python when a plugin misbehaves. Do not adopt it if you need a large hosted theme and plugin marketplace with commercial support, or if your team has no Python runtime on the build machine.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 13 days ago.
- What is it written in?
- Mainly Python, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- getnikola/nikola2,748 ★ · +2
| Repository | 2026-10-04 | 2026-11-21 |
|---|---|---|
| getnikola/nikola | 2.7k | 2.7k |
2 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The problem Nikola solves, and who it is actually for
Nikola is a static website and blog generator. The README states the premise plainly: in goes content, out comes a website, ready to deploy. The argument it makes for static output is that static websites are safer, use fewer resources, and avoid vendor and platform lock-in. That is the whole pitch, and it is a defensible one. A generated site is a directory of files. There is no database to patch, no runtime to keep warm, and no vendor whose pricing page can change under you.
The audience is narrower than the feature list suggests. Nikola is aimed at people who are comfortable in a terminal and who already have Python on the machine doing the building. The pyproject.toml sets requires-python to >=3.10 and classifies the project for Python 3.10 through 3.14. If your build environment is pinned to an older interpreter, that is a hard stop before anything else matters.
Where it differs from a generic static generator is the blog surface. The README lists blogs with tags, feeds, archives and comments, theming, image galleries where you drop files in a folder, syntax highlighting, and multilingual sites translated to 50 languages. Those are not extras bolted onto a page renderer. They are the reason the project exists, and they are why the plugin catalogue is as large as it is.
How Nikola builds a site: doit, tasks and the plugin layer
The build engine is doit, and this is the design decision that shapes everything else. The README credits doit for fast builds, and the dependency list in pyproject.toml confirms doit>=0.33.1 as a core requirement. doit is a task runner with dependency tracking, so Nikola does not walk every source file on every invocation. It models the site as a graph of tasks and only redoes the work whose inputs changed. On a blog with a few thousand posts, that distinction is the difference between a rebuild you run on every save and one you run before you leave for lunch.
The pipeline is conventional: source files in, templates rendered, output written to a directory you deploy. Mako is a declared dependency, which tells you the theming layer is Mako templates rather than Jinja2 or a bespoke syntax. Pygments handles syntax highlighting. Pillow and piexif are present for image work, which lines up with the gallery feature and with the fact that Nikola processes images at build time rather than shipping them raw.
Extensibility runs through blinker signals and a plugin system. The README points to a catalogue of available plugins and describes the core as small enough that programmers can understand all of Nikola core in a day. That claim is worth taking seriously in both directions. A small core is genuinely readable, and it also means behaviour you might expect to be built in lives in a plugin that has its own release cadence and its own compatibility story.
Installing Nikola and building a first site
The README gives the install commands directly. The base install is a single pip command, and it pulls the runtime dependencies listed in pyproject.toml, including doit, Pygments, Pillow, docutils, Mako, Markdown and lxml.
pip install NikolaIf you want the optional features, the README documents an extras target. This is where you get the pieces that are not in the base install.
pip install "Nikola[extras]"There is also a tests target, which the README describes as being for tests. That is aimed at contributors rather than users, and it is the combination you would install if you intended to run the project's own suite.
pip install "Nikola[extras,tests]"The README does not walk through creating a site in the text it provides; it points to https://getnikola.com/ for more information, and the quickstart link in the README is anchored to the reStructuredText input language. So the honest instruction is: install with pip, then follow the quickstart on the project site for the site-creation step. What you should expect after a successful install is a working command-line entry point and a dependency tree that includes doit and Mako. If pip resolves an older Python, the requires-python floor of 3.10 will stop the install rather than let it fail later.
Where Nikola gets awkward: plugins, Python version and build-time image work
The plugin system is the main risk surface. Because the core is deliberately small, a meaningful share of what a real blog needs arrives as a plugin, and each plugin is a separate piece of code with its own maintenance. The README links to the plugin catalogue but says nothing about compatibility guarantees between plugin releases and core releases. That silence is the thing to test before you commit, not after.
The Python floor is the second constraint. requires-python is >=3.10, and the classifiers stop at 3.14. If you are on a long-term-support distribution that ships 3.9, you are outside the supported range. This is not a subtle packaging detail; it determines whether the install works at all.
Third, image handling happens at build time. Pillow and piexif are runtime dependencies, and the gallery feature works by dropping files into a folder. That means the build machine needs the image libraries available and needs the CPU time to process them. A gallery of large photographs will make every build that touches those files slower, and the doit dependency tracking is what keeps that cost from being paid on unrelated edits. The README does not document rollback or a way to skip image processing, so plan for that cost rather than assuming you can switch it off.
Finally, the README's claim about a small codebase cuts both ways. It is a genuine advantage when you need to debug a rendering problem. It is not a substitute for documentation, and the README itself defers to the handbook and the project site for anything beyond installation.
Nikola compared with a JavaScript static site generator
The obvious alternative is a JavaScript-based generator such as Eleventy or Astro. The difference is not cosmetic. Those tools assume a Node.js toolchain, ship their templating and plugin ecosystem through npm, and generally expect you to bring your own blog features or install packages for them. Their build pipelines are typically configured in JavaScript, which means the configuration file is also a program.
Nikola's approach is Python-first and batteries-included. The blog features the README names, tags, feeds, archives, comments, galleries, multilingual output, are part of the project rather than a stack of third-party packages you assemble yourself. Configuration is data rather than code, and the build engine is doit rather than a Node task graph. The dependency list is short and readable: doit, Pygments, Pillow, python-dateutil, docutils, Mako, Markdown, unidecode, lxml, PyRSS2Gen, blinker, natsort, requests, piexif.
The practical difference shows up in team composition. If your team writes JavaScript and deploys from a Node build image, a Node generator will fit with less friction, and Nikola will require you to add a Python runtime to the pipeline. If your team writes Python, or if you specifically want reStructuredText as a first-class input alongside Markdown, the trade goes the other way. Nikola also accepts Wiki, BBCode, Textile and HTML as input languages, which is unusual and useful if you are migrating an archive from an older system.
Maintenance, releases and what the MIT licence does and does not give you
The repository is not archived, and the last push was on 2026-09-20. The most recent release listed is v8.3.3 from 2025-05-17, with v8.3.2 on the same day and v8.3.1 before that in 2024. The pyproject.toml declares Development Status :: 5 - Production/Stable and sets the version to 8.3.3, matching the release tag.
Upgrade cost is dominated by the plugin layer rather than the core. Core releases are versioned normally, and the dependency floors in pyproject.toml (doit>=0.33.1, Pygments>=2.4.2, Pillow>=9.1.0, docutils>=0.19, and so on) are minimums rather than pins, so an upgrade can pull newer transitive versions than the ones you tested against. If you depend on plugins, budget time to re-check them after a core bump. The README does not describe a deprecation policy or a support window, so there is no documented promise to lean on.
The licence is MIT, declared in LICENSE.txt and reflected in the classifier License :: OSI Approved :: MIT License. That permits commercial use, modification and redistribution provided the licence notice is preserved. It does not create any obligation on the maintainers to fix your bug, answer your question, or keep a plugin working. Treat the licence as permission, not as a service level. If you need a contractual relationship, the README does not point to one.
Editorial conclusion
Adopt Nikola if you write in reStructuredText or Markdown, want tags, feeds, archives and galleries without a database, and are comfortable reading Python when a plugin misbehaves. Do not adopt it if you need a large hosted theme and plugin marketplace with commercial support, or if your team has no Python runtime on the build machine. Before committing, verify the plugin you depend on still works with the current release, check that your Python version is 3.10 or newer, and confirm your deployment target can run the build step. The MIT licence keeps commercial reuse open, but that is a permission, not a support contract.
Frequently asked questions
What is Nikola and what is it used for?
Nikola is a static website and blog generator written in Python. It takes content in formats such as reStructuredText and Markdown and produces a deployable website, with blog features including tags, feeds, archives, comments and image galleries.
How do I install Nikola?
The README gives the command pip install Nikola. Optional features come from the extras target with pip install "Nikola[extras]", and the tests target is installed with pip install "Nikola[extras,tests]". The package requires Python 3.10 or newer.
Which input languages does Nikola accept?
The README lists reStructuredText and Markdown as input languages, and also Wiki, BBCode, Textile and HTML. Syntax highlighting is provided for almost any programming language or markup.
Does Nikola support multiple languages on one site?
Yes. The README lists multilingual sites, translated to 50 languages, as one of the project's features.
What licence is Nikola released under?
Nikola is released under the MIT licence, declared in LICENSE.txt and reflected in the PyPI classifier License :: OSI Approved :: MIT License.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/getnikola-nikola)Star history chart for your README
[](https://hysenlabs.com/projects/getnikola-nikola)Was this useful?