Help center overview
The help center is the public face of Docs: a standalone site that serves your published articles to anyone — customers, prospects, search engines — with no login.
What it is
A separate public site optimized for reading: fast, server-rendered pages built to be indexed by search engines, clean typography, and a navigation tree mirroring your spaces and collections.
Built from external-capable spaces — internal spaces are never exposed.
Hosted at
https://{subdomain}.helpin.centerby default, with articles at/articles/{article-slug}. You can also use a custom domain (e.g. help.yourcompany.com, same path shape) or a reverse-proxy path — see Help center customization & branding.
What customers see
Home page — a prominent search box and entry points into each public space.
Space pages — a sidebar with the collection tree and article list.
Collection pages — a landing list of articles within a collection.
Article pages — the rendered document with breadcrumbs, ToC, feedback widget, and related navigation.
Search — a dedicated search page with full-text matching across all published content.
Language switcher — when multiple locales are enabled.
What customers never see
Drafts and unpublished edits (public reads use published snapshots).
Internal spaces and team-only content.
Entity embeds and saved-view embeds (internal data blocks are stripped from public rendering).
Comments, version history, and internal links metadata.
How it relates to Docs
Docs concept | Help center concept |
|---|---|
External-capable space | Top-level nav section |
Collection | Sidebar group / collection page listing its articles |
Document | Article |
Publish (admins and above) | Goes live with a public slug |
Article metadata | SEO/OG fields per article |
The two stay in sync through snapshots: editing in Docs never changes the public site until you publish. That single rule makes the help center safe to author against — "draft boldly, publish deliberately."
Was this article helpful?