5aadd3d4f2
Add method get_translation(lang, key) into Config struct that retrieves translated term from parsed configuration or error when either desired language or key is missing. Use the new method in Trans struct implementing global Tera function trans(). Add unit test to cover both happy and error path for translation retrieval in both config and templates crate. |
||
---|---|---|
.github | ||
completions | ||
components | ||
docs | ||
src | ||
sublime_syntaxes | ||
sublime_themes | ||
test_site | ||
test_site_i18n | ||
.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
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.