Where to Find Zola Documentation, Themes, and Community Resources

Updated

Zola's official site (getzola.org) links directly to four resources: Docs, Themes, Forum, and GitHub. Use Docs to learn the CLI and template syntax, Themes to pick a ready-made site design, and the Forum or GitHub when you need help or want to follow the project. All four are reachable from the top navigation of the homepage.

The four official entry points

Resource What it's for When to use it
Docs Learning how Zola works: CLI usage, template engine, configuration Starting a site, looking up a specific feature or syntax
Themes Browsing and downloading community-made site themes You want a working look-and-feel without building templates from scratch
Forum Asking questions and reading discussions You're stuck on a problem or want to see how others solved it
GitHub Source code, issues, releases Reporting a bug, tracking changes, contributing

Docs

The documentation is the first stop for anything about how Zola behaves. The homepage describes the tool as designed to be intuitive "from the CLI to the template engine," and points you to the docs to judge that for yourself. Expect it to cover:

  • Installing and running the single Zola binary
  • Project structure and configuration
  • The template engine and how content is rendered
  • Built-in features the site highlights: Sass compilation, syntax highlighting, and table of contents

Zola's content format is "augmented Markdown" — fully templated, with internal links to make writing easier. The docs are where that syntax is spelled out.

Themes

The Themes section is a gallery of ready-made designs you can drop into a Zola project. This matters because Zola ships as one binary with no external dependencies, so a theme is essentially a set of templates and assets rather than a package you install through a separate toolchain. Browse here if you want a blog, knowledge base, or landing page look without authoring templates yourself.

Forum and GitHub

  • Forum — the place for questions and community discussion. Good for "how do I…" problems that aren't clearly bugs.
  • GitHub — the project's source and issue tracker. Use it to report bugs, check releases, or contribute. The site footer credits "Vincent Prouillet and contributors," and the GitHub link is where that development happens.

A practical order of operations

  1. Open Docs and follow the getting-started path to install the binary and create a project.
  2. Check Themes if you'd rather start from an existing design than a blank template.
  3. Search the Forum before posting — your question may already be answered.
  4. Go to GitHub only when you've confirmed something is a genuine bug or you want to track project changes.

All four links sit in the header of getzola.org, so you can reach any of them from the homepage without navigating deeper.