# Publish a help center

Any Library folder can become a public, branded docs site — written internally, published deliberately.

## From folder to site

1. In the Library, flag a folder as a **site** and give it a slug. The slug becomes the address: `{slug}.help.zerobuild.ai`.
2. Set the site's name, accent color, and whether search engines may index it.
3. **Publish.** Every doc in the folder (and its subfolders) goes live, except drafts you've explicitly held back.

The published site renders with a clean documentation template: your accent color and name, a sidebar built from your folder structure (top-level subfolders become sections), per-article table of contents, visitor-facing search, and light/dark modes.

## The visibility boundary

A doc inside a published site is public by default, with a per-doc override:

- **Inherit** — follows the site (public while the site is published)
- **Draft** — stays private even inside a live site; its URL returns 404
- **Published** — explicitly public

This boundary is enforced at the query layer, in one place, for every public surface — the site, its search, its sitemaps, and the [AI-readable endpoints](/ai-readable). Internal docs never leak into any of them.

## URLs that don't break

Each article gets a slug generated from its title — editable, and **never regenerated on rename**. Moving a doc within the site doesn't change its URL either; the sidebar reflects the new position, the address stays.

## One workspace, many sites

The site unit is the folder, not the workspace — publish a Help Center, a Policies site, and a Developer Docs site side by side, each with its own subdomain, name, and accent.