Adding, nesting, and reordering tree items

Documentation / Collections and content trees

Tree order is stored separately from page content. The collection's root file records which page is first, which pages are siblings, and which belong beneath another page. Titles, summaries, and availability remain in the individual page records.

Add an item

Select the intended collection in the pages area and choose Add page. Supply the navigation title and, optionally, the URL slug. Save the new page, then open it to write the header and body content.

Before rearranging a large tree, decide whether you are changing reading order or parentage. Moving a page between siblings changes order. Nesting it beneath another page changes its ancestry and can change its public address.

Change the tree

Open the reorder view for the selected collection. Drag an item to the indicated position before, after, or inside another item. Watch the indentation and placement indicator, then save the reordered structure. The tree prevents dropping an ancestor inside its own descendant.

Do not try to create hierarchy by editing a page slug alone. The root file is authoritative. When integrations submit a reordered tree, page entries contain page identities and children, not copied availability or navigation labels.

Verify the move

Reload the reorder view to confirm persistence. Open the parent and moved item, then follow the same route through the public tree navigation. Check descendants as well as the moved page because their computed paths may depend on the ancestor chain.

If the item disappears, check collection membership and page availability before recreating it. Reordering does not publish an unavailable page.

See Pages and navigation for visibility and internal links, and Search visibility and sharing for redirects after URL changes.