Choose a clear article layout
Adjust reading width, navigation and related guidance for a comfortable article experience.
On this page
Overview
Article pages stay on the existing KB renderer. Experience Builder only changes tokens, width, and chrome.
When to use this
Long answers need a comfortable reading column.
Where to find the controls
/support/article/{slug}/.
Who can make these changes
Public visitors. Helpful votes use the existing feedback API.
Before you begin
Article width 560–960px on KB Appearance.
Follow these steps
Write headings in the article so the TOC can list them. Attach KB tags for the footer cloud.
Settings reference
Headings provide article navigation. Related articles help readers continue to relevant published content. Article width controls the reading column.
Example workflow
A refunds article with H2s gets a sticky-style TOC on desktop themes that show it.
Good practices
Still-need-help uses the Global Ticket Form CTA, not a hardcoded field list.
Important considerations
Do not paste untrusted HTML into hero fields.
If something does not work
Missing TOC: the article has no heading tags.