The `public/` directory from `zola build`. The entry `index.html` becomes the report body, and the CSS, JS, images and fonts upload as assets with their references rewritten to the uploaded copies.

Do I need to set base_url?

For a preview, build with `zola build --base-url /` so links and asset paths are not pinned to a hostname the preview is not being served from. That single flag is the usual cause of a preview whose stylesheet 404s.

Does Zola's built-in search work at the link?

The search index is a generated file in `public/`, so it uploads with the rest and the client-side search runs — scripts execute inside a sandboxed iframe.

Why not run zola serve and share that?

Because `zola serve` binds to your machine and lives as long as your terminal does. A reviewer in another timezone needs a URL that survives you closing the laptop.

How do I update the preview?

PATCH the same report id after each build. The reviewer's link shows the current build, earlier builds stay as revisions, and their comments carry over.

Share a Zola site preview

Zola builds a site in one binary with no Node install and no dependency tree, which makes the contrast sharper than usual: the build takes milliseconds, and getting one colleague to look at the result takes twenty minutes of deciding where to put it.

Publish the build

zola build --base-url /

Drag public/ (or a zip of it) into the app:

index.html becomes the report body.
CSS, JS, images, fonts and the generated search index upload as assets with their references rewritten to the uploaded copies — the step that fails when you open public/index.html from disk and every root-relative path resolves against your filesystem. See broken CSS in a shared report.
Scripts run inside a sandboxed iframe, so a theme toggle or the built-in search keeps working.

--base-url / is worth the flag: a preview build should not assume the hostname it will eventually be served from.

Private by default

A pre-launch site is not something to leave on a guessable URL. Every report is private until you change it — team, email-domain gate, named reviewers, or a password-protected link for a client. See the sharing model.

Feedback lands on the page

Anchored threads on the paragraph, the image, the nav item — see commenting on HTML.
Revisions. Rebuild and PATCH the same report id; the reviewer sees the new build at the URL they already have, with the previous one still there.
An agent can read the comments back through MCP.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total — a site with a page per taxonomy term can exceed 500 files. Build a section for review when it does.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Create your first report →