Tree landing pages, branch pages, and item pages

Documentation / Collections and content trees

A tree can contain a collection landing address, branch pages with children, and leaf pages without children. These addresses do not necessarily render the same way. Test the routing behavior before writing content that readers must see at a parent address.

Collection landing addresses

The collection's base path is its shared entry address. If no page resolves there, the engine can redirect that address to the first tree item. Creating a collection therefore does not automatically create a written landing page.

If you need a collection introduction, arrange an actual page and listing for that role. Verify the resulting address rather than assuming the collection name becomes page content.

Branches and leaves

A branch is a page with child entries in the root file. For sequential-root item routing, the engine redirects branches to their first child unless the root allows parent content. Additional parent-page routing also considers listing blocks. These rules mean a page can exist in the CMS while its public address leads elsewhere.

The configuration API supports parent-content behavior, but the basic collection form does not show a corresponding switch. Ask an administrator to verify the collection configuration when readable topic overviews are required. Do not look for a guessed control label.

A leaf normally renders its own header and body, with any applicable template content. It remains subject to its availability and publication date.

Check the reading path

Visit the base address, each important branch, and one leaf beneath every branch. Confirm the final address, visible introduction, child listing, and back-navigation. Repeat in each supported language because translated slugs can differ.

See Templates and reusable content and Languages and translations.