Understanding includeDocs and IDs in Wayfinder Menus

Wayfinder can render menus from a tree branch, but some designs need a hand-picked set of resource IDs instead. That is where people often mix up includeDocs, normal branch traversal, and static document lists.

The most important thing to remember is that Wayfinder still follows tree logic. Including a resource ID does not erase the structure the menu builder is working with.

When Problems Appear

• a menu item appears in an unexpected position
• an included resource seems to inherit the wrong level
• template assumptions do not match actual tree depth

If a menu behaves strangely, debug the data source first: which branch starts the menu, which IDs are injected, and how the chunk interprets level classes. In most cases the markup is wrong only because the menu tree was misunderstood.