The public documentation site

Your published articles are also a public documentation site — navigation, table of contents, rendered Markdown — with nothing extra to set up.

https://askvoro.com/~/YOUR_WORKSPACE_HANDLE/YOUR_KNOWLEDGE_BASE_SLUG

Every article gets its own URL, so you can link to a specific page from an email, a receipt, or a support reply. Append .md to an article URL when you need its raw Markdown instead of the rendered page.

Published means published#

The site shows only published articles, and that's enforced before an article body is ever read — not filtered in the page afterwards. An unpublished draft cannot appear here, including by guessing its URL.

The knowledge base must also have public visibility. An internal base at the same URL requires a signed-in workspace member with article access, and a hidden base never renders there.

What it's good for#

• Linking a customer to the full answer instead of pasting it into chat.
• Letting people read your help center without opening the widget.
• Getting your documentation indexed by search engines.

Sections become navigation#

Section titles and positions become the site's navigation, and article order within a section carries over. Organise once, and the widget, the docs site and the AI all follow.

Headings inside an article become its table of contents, so use ## and ### in a sensible hierarchy rather than skipping levels for the look of it.

Current limits#

Worth knowing before you point customers at it:

• No custom domain yet — docs are served from askvoro.com.
• No search on the docs site. The widget is where search happens.
• No per-article visibility. Access is selected for the whole knowledge base (public, internal, or hidden), while each record still has its own published/draft state.

If you need a fully branded documentation site today, link to these pages from your own site rather than treating them as your primary docs home.