The default configuration is sufficient to get Zola running locally but not more than that. It follows the philosophy of paying for only what you need, almost everything is turned off by default.
To change the configuration, edit the
If you are not familiar with TOML, have a look at the TOML spec.
⚠️ If you add keys to your
config.toml, you must pay attention to which TOML section it belongs to. A TOML section starts with a header, e.g.
[search], and ends at the next section or EOF.
Here are the current
base_url variable is mandatory. Everything else is optional. All configuration variables
used by Zola as well as their default values are listed below:
Zola currently has the following highlight themes available:
Zola uses the Sublime Text themes, making it very easy to add more. If you want a theme not listed above, please open an issue or a pull request on the Zola repo.
Alternatively you can use the
extra_syntaxes_and_themes configuration option to load your own custom themes from a .tmTheme file.
See Syntax Highlighting for more details.
By default, Zola will turn every path, taxonomies and anchors to a slug, an ASCII representation with no special characters. You can however change that strategy for each kind of item, if you want UTF-8 characters in your URLs for example. There are 3 strategies:
on: the default one, everything is turned into a slug
safe: characters that cannot exist in files on Windows (
<>:"/\|?*) or Unix (
/) are removed, everything else stays
off: nothing is changed, your site might not build on some OS and/or break various URL parsers
Since there are no filename issues with anchors, the
off strategies are identical in their case: the only change
is space being replaced by
_ since a space is not valid in an anchor.
Note that if you are using a strategy other than the default, you will have to manually escape whitespace and Markdown
tokens to be able to link to your pages. For example an internal link to a file named
some space.md will need to be
some%20space.md in your Markdown files.