Building Breadcrumbs That Preserve Hierarchy Without Nested URLs

Some projects want clean flat URLs but still need a clear hierarchy in breadcrumbs and dropdown navigation. That means the URL structure and the content structure should not be treated as the same thing.

In Evolution CMS, the right way to handle this is to let the resource tree define hierarchy and let the breadcrumb or menu snippet render that structure, even if friendly URLs are not nested.

What this means in practice

• Keep the real parent-child relations intact in the document tree.
• Use breadcrumb templates that render the chain based on document ancestry.
• Let Wayfinder or Breadcrumbs output the hierarchy independently of the final URL shape.
• Avoid forcing nested paths only to make breadcrumbs look “correct”.

This gives you the best of both worlds: editorial structure remains clear, menus and breadcrumbs stay meaningful, and the visible URL can remain short or flat where the project requires it.

When teams separate hierarchy from URL appearance, navigation components become much easier to maintain.