Build a documentation library with a three-level tree

Guides

Design the three levels

Build a sequential collection with three meaningful levels: Documentation, topic overview, and article. Each overview should help readers choose their next page, not act as an empty navigation label.

You need administrator access, approved English content, and a stable collection base path. Start with a small outline: Documentation contains Getting started and Account management; Getting started contains Creating an account and Signing in. Use only subjects the product actually supports. Write a one-sentence purpose for every page before building the tree.

Decide where the library landing page belongs. A collection base path and a top-level page are separate concepts. Avoid creating an extra /documentation segment unintentionally when the collection base path already supplies it. Resolve the actual public URLs before circulating links.

Build the collection and pages

1. Open Collections > New collection. Enter a recognizable Name and the intended Base path, then choose Sequential (tree hierarchy) under Type. Save and note the collection you created.
2. In Pages, select that collection and add the landing page, topic pages, and articles. Keep a real header on every regular page. For each topic overview, explain who the topic is for and link to its initial articles. For each article, state an outcome and any prerequisites.
3. Arrange the hierarchy in the page tree. Drop an item in the middle area of its intended parent to nest it; positions near the top or bottom place it before or after. Keep the requested three levels rather than adding unnecessary intermediate folders. Review the saved tree after each small group of changes.
4. Set concise Nav Title values and useful summaries in page metadata. Structure belongs in the root tree, while titles and access settings belong to individual pages. Do not attempt to control ancestry by embedding full parent paths in every article slug.
5. Add Page List blocks where readers need generated navigation. The block's configuration uses different presets for sequential and dated collections. Select this collection and a suitable sequential presentation, then check whether the displayed scope matches the intended overview. Use explicit internal page links for any route the selected listing does not express clearly.
6. Save pages and verify Availability before launch. A public overview should not promise access to an unfinished or protected article. Keep menu membership and content availability under review as the library grows.

Test navigation in both directions

Open the landing page without the editor and follow a complete route to an article. Check topic links, parent navigation where present, and the browser's Back button. Verify deep URLs directly, including on a phone. Confirm that page titles, hierarchy, and links describe the same structure.

If an article appears under the wrong topic, fix the root tree rather than editing only its URL. If a listing is empty, check the selected collection, scope, availability, and date. Read collections and content trees, pages and navigation, and search visibility.