Public article pages

The article page is where customers actually read. It renders your published snapshot with everything needed for a self-serve answer: clean typography, navigation, metadata, and feedback.

Anatomy of an article page

• Breadcrumb — Space → Collection → Article, locale-aware.

• Title and excerpt — from the published snapshot; the icon renders beside the title.

• Rendered content — headings, text, lists, tables, callouts, code blocks, images, video embeds, ToC blocks, and sanitized HTML blocks. Entity and saved-view embeds are stripped from public pages.

• Feedback widget — "Was this helpful?" with helpful / not-helpful actions.

• Sidebar navigation — the collection tree, so readers can move to related articles without returning to search.

• Footer — brand footer with the support email for escalation.

Article metadata

Each article carries its own public metadata, editable from the Docs publish panel:

• SEO title and description — search engine titles/snippets (falls back to title/excerpt).

• OG title, description, and image — how links preview in Slack, X, and chat.

• Excerpt — used in collection listings and search results.

View and feedback counts

Articles track views, helpful, and not-helpful counts. These surface in the article metrics (and in Docs for authors), powering the article quality loop — see Article feedback.

Preview before publish

A preview (available whatever the document's status) lets authors see exactly how the article will look on the public site. Use it to check tables, callouts, and images before going live.

Performance

Article pages serve the published version of each article as fast, server-rendered pages — good for readers and good for SEO (see SEO for public docs).