f5a200e64c
This commit fixes a bug in the documentation for the feeds page which shows how to use the RSS block to enable feed autodiscovery. The bug used an em space character instead of a space in one part of the code snippet. If a user were to copy the code snippet into their code as directed, the Zola build would fail with a parse error. The em space appears identical to a regular space in monospaced fonts, making the error seem mysterious or incorrect. I believe the em space was used in order to prevent the shortcode from rendering, as the code snippet is just meant to show what the shortcode looks like. However, it is possible to escape the shortcode so that it renders correctly without causing confusion for the user who expects to be able to copy and paste it. This commit replaces the em space in both code snippets with regular spaces and escapes the shortcodes. |
||
|---|---|---|
| .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.