46ee256ba4
Clippy is returning some warnings. Let's fix or explicitly ignore them. In particular: - In `components/imageproc/src/lib.rs`, we implement `Hash` explicitly but derive `PartialEq`. We need to maintain the property that two keys being equal implies the hashes of those two keys are equal. Our `Hash` implementations preserve this, so we'll explicitly ignore the warnings. - In `components/site/src/lib.rs`, we were calling `.into()` on some values that are already of the correct type. - In `components/site/src/lib.rs`, we were using `.map(|x| *x)` in iterator chains to remove a level of indirection; we can instead say `.copied()` (introduced in Rust v1.36) or `.cloned()`. Using `.copied` here is better from a type-checking point of view, but we'll use `.cloned` for now as Rust v1.36 was only recently released. - In `components/templates/src/filters.rs` and `components/utils/src/site.rs`, we were taking `HashMap`s as function arguments but not generically accepting alternate `Hasher` implementations. - In `src/cmd/check.rs`, we use `env::current_dir()` as a default value, but our use of `unwrap_or` meant that we would always retrieve the current directory even when not needed. - In `components/errors/src/lib.rs`, we can use `if let` rather than `match`. - In `components/library/src/content/page.rs`, we can collapse a nested conditional into `else if let ...`. - In `components/library/src/sorting.rs`, a function takes `&&Page` arguments. Clippy warns about this for efficiency reasons, but we're doing it here to match a particular sorting API, so we'll explicitly ignore the warning. |
||
|---|---|---|
| .github | ||
| ci | ||
| completions | ||
| components | ||
| docs | ||
| src | ||
| sublime_syntaxes | ||
| sublime_themes | ||
| test_site | ||
| test_site_i18n | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| appveyor.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 | |
|
|
|
| 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 the multi-language support as it only has a basic support and does not offer (yet) things like i18n in templates.
Pelican notes
Many features of Pelican are coming from plugins, which might be tricky to use because of version mismatch or lacking documentation. Netlify supports Python and Pipenv but you still need to install your dependencies manually.