0.9.0 | Updated: 05 Oct 2019



Downloads of v 0.9.0:



Software Author(s):

  • Vincent Prouillet
  • zola contributors

zola 0.9.0

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install zola, run the following command from the command line or from PowerShell:


To upgrade zola, run the following command from the command line or from PowerShell:


To uninstall zola, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:

choco upgrade zola -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade zola -y --source="'STEP 3 URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure zola installed
    name: zola
    state: present
    version: 0.9.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'zola' do
  action    :install
  version  '0.9.0'
  source   'STEP 3 URL'

See docs at https://docs.chef.io/resource_chocolatey_package.html.

    Name: zola,
    Version: 0.9.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.

cChocoPackageInstaller zola
   Name     = 'zola'
   Ensure   = 'Present'
   Version  = '0.9.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

package { 'zola':
  provider => 'chocolatey',
  ensure   => '0.9.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

salt '*' chocolatey.install zola version="0.9.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 05 Oct 2019.


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.

Supported content formats

  • Zola: markdown
  • Cobalt: markdown
  • Hugo: markdown, asciidoc, org-mode
  • Pelican: reStructuredText, markdown, asciidoc, org-mode, whatever-you-want

Template engine explanation

Cobalt gets ~ as, while based on Liquid, the Rust library doesn't implement all its features but there is no documentation on what is and isn't implemented. The errors are also cryptic. Liquid itself is not powerful enough to do some of things you can do in Jinja2, Go templates or Tera.

Hugo gets ~. It is probably the most powerful template engine in the list after Jinja2 (hard to beat python code in templates) but personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased.

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.


As the documentation site is automatically built on commits to master, all development
should happen on the next branch, unless it is fixing the current documentation.

If you want a feature added or modified, please open an issue to discuss it before doing a PR.

$ErrorActionPreference = 'Stop'

$packageName= $env:ChocolateyPackageName
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url      = "https://github.com/getzola/zola/releases/download/v$($env:ChocolateyPackageVersion)/zola-v$($env:ChocolateyPackageVersion)-x86_64-pc-windows-msvc.zip"

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  url           = $url
  checksum      = '1A69861F6602579AC0391E63CDD14F143B1F1E373B34CA8A3A4BD98C22151DF5'
  checksumType  = 'sha256'

Install-ChocolateyZipPackage @packageArgs

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
zola 0.8.0 91 Wednesday, July 17, 2019 Approved
zola 0.7.0 96 Sunday, April 28, 2019 Approved
zola 0.6.0 73 Monday, March 25, 2019 Approved
zola 0.5.0 142 Saturday, November 17, 2018 Approved

0.9.0 (2019-09-28)


  • Add --drafts flag to build, serve and check to load drafts. Drafts are never loaded by default anymore
  • Using fit in resize_image on an image smaller than the given height/width is now a no-op and will not upscale images anymore


  • Add --open flag to open server URL in default browser
  • Fix sitemaps namespace and do not urlencode URLs
  • Update livereload
  • Add hard_link_static config option to hard link things in the static directory instead of copying
  • Add warning for old style internal links since they would still function silently
  • Print some counts when running zola check
  • Re-render all pages/sections when anchor-link.html is changed
  • Taxonomies can now have the same name in multiple languages
  • zola init can now be create sites inside the current directory
  • Fix table of contents generation for deep heading levels
  • Add lang in all templates context except sitemap, robots
  • Add lang parameter to get_taxonomy and get_taxonomy_url
  • Rebuild whole site on changes in themes changes
  • Add one-dark syntax highlighting theme
  • Process images on changes in zola serve if needed after change

0.8.0 (2019-06-22)


  • Allow specifying heading IDs. It is a breaking change in the unlikely case you are using {#..} in your heading
  • Internal links are now starting by @/ rather than ./ to avoid confusion with relative links
  • Latest Tera version now cares about where the safe filter is, always put it at the end of an expression.


  • Fix image processing not happening if called from the template
  • Add a zola check command to that validates the site and checks all external links
  • Sections can have aliases as well
  • Anchors in internal links are now checked for existence

0.7.0 (2019-04-28)


  • Remove --base-path option, it broke serve on Windows and wasn't properly tested


  • Strip wrapping whitespaces from shortcodes
  • Sort sitemap elements by permalink`

0.6.0 (2019-03-25)


  • earlier/later and lighter/heavier are not set anymore on pages when rendering
    a section
  • The table of content for a page/section is now only available as the toc variable when
    rendering it and not anymore on the page/section variable
  • Default directory for load_data is now the root of the site instead of the content directory
  • Change variable sent to the sitemap template, see documentation for details


  • Add support for content in multiple languages
  • Lower latency on serve before rebuilding from 2 to 1 second
  • Allow processing PNG and produced images are less blurry
  • Add an id (zola-continue-reading) to the paragraph generated after a summary
  • Add Dracula syntax highlighting theme
  • Fix using inline styles in headers
  • Fix sections with render=false being shown in sitemap
  • Sitemap is now split when there are more than 30 000 links in it
  • Add link to sitemap in robots.txt
  • Markdown rendering is now fully CommonMark compliant
  • load_data now defaults to loading file as plain text, unless format is passed
    or the extension matches csv/toml/json
  • Sitemap entries get an additional extra field for pages only
  • Add a base-path command line option to build and serve

This package has no dependencies.

Discussion for the zola Package

Ground Rules:

  • This discussion is only about zola and the zola package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or zola, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus