Publishing & the Docs Site

Publishing & the Docs Site

Once your content is written, Zingasolve publishes it to a fast, self-contained
documentation site. This article covers how visibility, publishing, addresses,
custom domains, PDF export, and search fit together.

Draft vs publish

Editing is always private. Save draft keeps your working copy without
touching the live site. Publish freezes the current content as an immutable
version and makes it live for the current locale. Because the site serves
published versions only, readers never see half-finished edits, and every
published version is preserved in the article's history.

Locales publish independently, so you can ship an updated English page and
publish its translations later. A translation that lags behind a newer source
version is flagged outdated in the editor until you republish it.

Visibility levels

Every Space sets a baseline visibility, and each collection or article can
override it (or inherit it from its parent):

Public pages are cacheable and fast; anything gated is rendered per reader.
Restricting content is covered in detail in Access Control.

The docs micro-site

Published Spaces are served from the docs micro-site at:

https://docs.zingasuite.com/<your-site-slug>

The site is a clean, themeable docs layout — a sidebar navigation tree built
from your collections and articles, the article body, and a top bar with your
site name and a sign-in affordance. The navigation only lists pages the current
reader is allowed to open.

The entity hub

If you publish more than one manual, you can turn on an entity hub — a
landing page that lists all of your manuals as cards. The hub lives at its own
globally unique address:

https://docs.zingasuite.com/<your-hub-slug>/

Each manual is then served under the hub at its own slug (for example
.../help-center/ and .../api-docs/). You can give the hub a title and
subtitle to brand the landing page, and the hub only shows manuals the
reader is allowed to enter.

Branding

You can brand both the hub and its manuals with a logo, custom CSS, and
custom header and footer HTML. Header and footer markup supports
placeholders that resolve to live URLs at render time, so your menus survive slug
changes:

Custom domains

You aren't limited to the default address. You can connect a custom domain
(for example docs.acme.com) to a single manual or to your hub. A custom hub
domain serves every manual under it; a custom manual domain serves just that one.
Once the domain is verified, your docs are served over HTTPS on your own brand.

PDF export

Any manual can be exported to a print-ready PDF from its workspace. The
export renders your chapters and pages, resolves video, annexure, and reusable-
content references, and appends your annexures — each with a cover sheet, and PDF
files merged in after it. You can tune the output with per-manual, per-chapter,
and per-section PDF settings (headers, footers, CSS, cover and back pages, page
size, and orientation).

Search and reader feedback

Every published site includes full-text search across your published
content, so readers can find pages by keyword. Each article also shows a "Was
this helpful?" prompt so you get signal on which pages work and which need
attention. Where enabled, the same content grounds the AI support assistant's
answers.

Going live checklist

1. Set each Space, collection, and article to the right visibility.
2. Publish the content — every locale you want live.
3. Choose your address: the default docs.zingasuite.com/<site-slug>, an
   entity hub, and/or a custom domain.
4. Add your branding (logo, header, footer, CSS).
5. Export a PDF if you distribute an offline manual.