d571dea8c3
* Per section/subsection feeds * Added `generate_feed` variable to section front matter. * Generate atom/rss feeds for sections/subsections that have the `generate_feed` variable set to true (false by default); this works independent of the `generate_feed` variable in the root `config.toml` file, however, the name (and template) of the feed file for each section is the same as `feed_filename` in `config.toml`, just located in the root of each section. * Slightly edited `atom.xml` and `rss.xml` so that they include the section title (if any), and the url of a section, if it's a section feed. * Section feeds: tests * Changed a couple of sections' front matter in order to generate feeds for them for the test. * Changed the can_build_feed test in site package to can_build_feeds and included some assertions to make sure that section feeds are generated when requested. * Section feeds: documentation * Added information about the section front matter variable `generate_feed` in the section content page. * Added information about section feeds in the feeds template page. * Section feeds fix: use section.path for feed path |
||
|---|---|---|
| .github | ||
| completions | ||
| components | ||
| docs | ||
| src | ||
| sublime | ||
| test_site | ||
| test_site_i18n | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| azure-pipelines.yml | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| EXAMPLES.md | ||
| is-ehh.svg | ||
| is-no.svg | ||
| is-yes.svg | ||
| LICENSE | ||
| netlify.toml | ||
| README.md | ||
| rustfmt.toml | ||
| snapcraft.yaml | ||
zola (né Gutenberg)
A fast static site generator in a single binary with everything built-in.
Documentation is available on its site or
in the docs/content folder of the repository and the community can use its forum.
Comparisons with other static site generators
| Zola | Cobalt | Hugo | Pelican | |
|---|---|---|---|---|
| Single binary |  |
|
|
 |
| Language | Rust | Rust | Go | Python |
| Syntax highlighting | |
|
|
|
| Sass compilation | |
|
|
|
| Assets co-location | |
|
|
|
| Multilingual site |  |
|
|
|
| Image processing | |
|
|
|
| Sane & powerful template engine | |
|
|
|
| Themes | |
|
|
|
| Shortcodes | |
|
|
|
| Internal links | |
|
|
|
| Link checker | |
|
|
|
| Table of contents | |
|
|
|
| Automatic header anchors | |
|
|
|
| Aliases | |
|
|
|
| Pagination | |
|
|
|
| Custom taxonomies | |
|
|
|
| Search | |
|
|
|
| Data files | |
|
|
|
| LiveReload | |
|
|
|
| Netlify support | |
|
|
|
| Vercel support | |
|
|
|
| Breadcrumbs | |
|
|
|
| Custom output formats | |
|
|
|
Supported content formats
- Zola: markdown
- Cobalt: markdown
- Hugo: markdown, asciidoc, org-mode
- Pelican: reStructuredText, markdown, asciidoc, org-mode, whatever-you-want
explanations
Hugo gets for the template engine because while it is probably the most powerful template engine in the list (after Jinja2) it personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased.
Zola gets for multi-language support as it only has a basic support and does not (yet) offer things like i18n in templates.
Pelican notes
Many features of Pelican come from plugins, which might be tricky to use because of a version mismatch or inadequate documentation. Netlify supports Python and Pipenv but you still need to install your dependencies manually.