Collection base paths and item URLs

Documentation / Collections and content trees

A collection's Base path is the shared prefix for its public addresses. An item's stored URL value is its own slug, not necessarily its complete public address. Beeboo combines the collection configuration, page metadata, and tree hierarchy when resolving a request.

Read an address correctly

For a dated collection at /news, an item with the slug /release-notes appears at /news/release-notes. Sequential collections can also accumulate ancestor slugs. In a tree at /doc, a child /installation beneath /setup can appear at /doc/setup/installation.

The root file supplies the parent-child relationship. Typing a slash into a URL is not a substitute for nesting the page in the collection tree. Likewise, a stored pageType is not required: the implementation derives collection behavior from membership and configuration.

Edit with care

Set the collection prefix in Base path. Set the item's own URL in its page settings. When the form displays a fixed folder prefix, edit the remaining slug rather than repeating the prefix.

For translated collections, a secondary language can have its own base path and item slugs. A language prefix is added to the computed public address. Translations retain the same page identity even when their addresses differ.

Check links after changes

Open both the full public address and links from listings or tree navigation. Test a nested item after moving its parent because the computed address may change. Use page-picker links where available: Beeboo stores internal page references by identity and resolves their localized destinations.

For external links to old addresses, configure and test redirects separately. See Pages and navigation and Search visibility and sharing.