Install zola with Homebrew, apk, MacPorts, Nix, pacman, scoop, winget, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• zola

Project history

Creator Vincent Prouillet wrote that Gutenberg began in May 2015, shortly after Rust 1.0, as a way for him and a friend to learn Rust by building a static site generator. The project was also entangled with Tera, the template engine Prouillet built after finding no Rust template library he liked for the job.

Gutenberg grew beyond the creator's original expectation of a private learning project. By 2018, the name collided with Project Gutenberg, CSS projects, and especially WordPress's Gutenberg editor, so the project was renamed Zola with the 0.5.0 release. The README still labels it "zola (ne Gutenberg)" and describes the project as an all-included static site generator.

Adoption history

Zola entered the same broad SSG conversation as Hugo, Jekyll, and Pelican, but its adoption pitch was different: Rust implementation, a dependency-light install story, and features that often require separate tooling elsewhere. The rename was explicitly complicated by the fact that Gutenberg was already present in package managers and deployment platforms.

Its audience has been strongest among developers who want a static site generator without a Node, Ruby, Python, or Go template stack. Zola's official docs frame it as comparable to Hugo, Pelican, and Jekyll while emphasizing a single executable and Tera-based templating.

How it is used

A typical Zola workflow is to keep site content in Markdown, define templates with Tera, and use a small config file such as config.toml or zola.toml. The CLI builds static files for deployment and can serve locally with live reload during editing.

Zola is commonly used for blogs, documentation sites, knowledge bases, landing pages, and book-like sites. Its package appeal comes from bundling Sass compilation, syntax highlighting, table-of-contents generation, internal links, taxonomies, search, and deployment-oriented static output into one tool.

Why package nerds care

Zola is a clean example of the post-Jekyll static-site-generator packaging ideal: install one binary, avoid runtime dependency stacks, and get a reproducible local build command. That makes it especially attractive in package indexes where users compare tooling by executables, config files, and build ergonomics.

The Gutenberg-to-Zola rename is also a package-history lesson: names that work for a small open-source project can become liabilities once search, package managers, and deployment services start to matter.

Timeline

• 2015: Gutenberg work begins after Rust 1.0 as a Rust-learning static site generator project.
• 2016: The current public repository history begins after earlier work was reset around Tera and the SSG implementation.
• 2018: The project opens a rename discussion because WordPress Gutenberg and other name collisions make discovery difficult.
• 2018: Zola 0.5.0 ships under the new name, carrying the Gutenberg user base forward.
• 2020s: Zola continues as a single-binary Rust SSG used for blogs, documentation, knowledge bases, and static web publishing.

Related projects

• Hugo: the Go SSG that influenced Zola and helped define the single-binary static site generator niche.
• Jekyll and Pelican: older SSGs that Zola documentation uses as comparison points.
• Tera: Zola's Rust template engine, developed alongside the early project.
• Cobalt: another Rust SSG often compared with early Gutenberg/Zola in the Rust static-site ecosystem.

Sources

• https://github.com/getzola/zola
• https://www.getzola.org/documentation/getting-started/overview/
• https://www.vincentprouillet.com/blog/releasing-zola-0-5-0/