Creating a tree collection

Documentation / Collections and content trees

A tree collection is a sequential collection whose root file records an explicit hierarchy. It suits documentation, reference material, or a resource library where parent topics and reading order help readers find a page.

Create the structure

Choose New collection, enter Name and Base path, and select Sequential (tree hierarchy) under Type. Save the collection, then select it in the pages area before using Add page.

Start with a small outline: a few topic pages and one or two articles under each topic. Add meaningful titles and short URL slugs. Use the collection's reorder tree to place articles beneath the appropriate topic. A page's title and slug do not establish its parent.

Decide what branches should do

A parent can represent a navigable overview or a folder-like step in the tree. These are different reading experiences. The engine can redirect a parent item to its first child when the collection does not allow parent content. The basic collection form does not expose every advanced root option, so ask an administrator to verify parent-content configuration when you need readable topic overviews.

Keep a real header on regular overview and article pages. Do not replace the required page header with a body section simply because the page belongs to a tree.

Validate before expanding

Open the collection base address, a topic address, and a nested article. Confirm whether each branch renders or redirects. Place a collection-listing block on a page, or use a template with tree navigation, and test the hierarchy on a narrow screen.

See Templates and reusable content and Page anatomy and the managed editor before building the full library.