Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Future consideration
Categories Editing
Created by Guest
Created on Mar 6, 2020

Allow container pages that don't generate a URL segment

Some functionality cascades down the page tree, like approvals or permissions. Sometimes you want to group pages together so you can apply values and functionality to branches of pages, but these necessarily affects the URL, since any page generates a new URL segment.

"Container" pages can't be accessed directly, but they still generate a URL segment, so they can't be transparently used for grouping content.

It would be helpful to allow a type of container page that doesn't generate a URL segment. When ancestors are collected to form a URL for a descendant page, this type of page could simply be skipped and its segment omitted.