Documentation pages
The Documentation editor lets you write and publish a structured help site — and every published page is automatically pulled into your chatbot's knowledge base. Open it from Dashboard → Documentation.
This is the right tool when you want content that lives in two places at once: a public help center at
/docs/[slug]🖼️ [Image] — The Documentation editor: page tree on the left, rich editor in the center, page settings on the right.
The page tree
The left panel is a hierarchical tree of all your pages. To create one, add a new page and give it a Title; optionally choose a Parent so it nests under another page. You can also Duplicate or Delete any page from its context menu.
Writing: rich vs. markdown
The center pane edits a single markdown document, with two interchangeable views:
- Rich (WYSIWYG) — format visually with the toolbar, slash commands, links, and embedded images.
- Markdown — edit the raw source directly.
Switching between the two is lossless, so you can write however you prefer and flip views any time.
Autosave
Changes save automatically about 2 seconds after you stop typing — there's no Save button. An indicator shows Saving / Saved so you always know the current state.
🎬 [Video] — Typing in the rich editor, switching to markdown view, and watching autosave fire.
Publishing
A page is a private draft until you Publish it. Publishing does two things:
- Makes the page live on your public docs site at .text
/docs/[slug] - Syncs the page content into the knowledge base and generates embeddings, so the chatbot can answer from it.
Unpublish reverses both — the page leaves the public site and stops being used by the bot. Set as Homepage marks one published page as the landing page of your docs site.
When you publish a page, the knowledge sync only re-embeds if the content actually changed (tracked by a content hash). Re-publishing an unchanged page is cheap and won't burn embedding cost.
Documentation page vs. manual knowledge entry
Use whichever fits the content:
| Use a documentation page when… | Use a manual Text entry when… |
|---|---|
| You want the content public on your text | The content is internal-only knowledge for the bot. |
| It's a structured article with headings, images, links. | It's a short snippet, FAQ answer, or quick gap fix. |
| You want it to live in an organized page tree. | You just need it searchable, fast. |
Both end up in the same knowledge base and are retrieved the same way — see How retrieval works.