Organize documentation categories

Updated May 22, 2026

How categories work in documentation

Each category in a documentation maps to one navigation tab on the public docs site. When you click a tab, the page tree for that category appears on the left. If there is only one category, the tab bar is hidden — the single category's pages are shown directly, giving a cleaner reading experience for simple docs.

Inside each category, pages are organized as a tree — root pages at the top level, with child pages nested underneath. There is no hard limit on tree depth.

Create a category

  1. Open your documentation (Dashboard → Documentation → [your docs]).
  2. Click New Category.
  3. Enter a name (shown as the tab label on the public site) and an optional description.
  4. Save.

Order your categories

Categories are ordered by weight — lower weight numbers appear first (leftmost tab). To reorder:

  • Open the row's three-dot menu next to a category and choose Move Up or Move Down. The order field shown in the categories table is read-only.

Nested pages within a category

Pages within a category form a hierarchy. A few things to know:

  • Root pages are the top-level entries in the tree. They can have child pages, which can have their own children.
  • Empty parent pages are allowed — a page without content acts as a folder-only container. Its children are still navigable and readable.
  • To add a child page, open the three-dot menu on the parent page and choose Add Child. For pages that already have children, an inline + Add Child link also appears at the end of the child list.
  • To reorder pages, use the Move Up / Move Down options in the page's three-dot menu — this reorders siblings within the same parent.

Delete a category

Open the three-dot menu next to a category name and choose Delete.

Deleting a category permanently removes all its pages. This cannot be undone. Unpublish the category first if you want to take it offline temporarily without losing content.

For publishing categories and pages, see Publish documentation to a public URL.

Did this article answer your question?