Blog Sections Open

Building Multi-Level Menus with Wayfinder

Wayfinder becomes much easier to work with once you treat the menu markup as templates rather than trying to force static HTML directly into the call.

This donor showed a long static navigation example with multiple levels, dropdown wrappers, and repeated patterns. That is exactly the type of menu that should be translated into Wayfinder row templates instead of being maintained by hand.

Recommended Approach

  • Split the navigation into row, inner row, parent row, and outer wrapper templates.
  • Map the original classes and IDs to Wayfinder template chunks.
  • Test the two-level case first, then extend to deeper nesting only after the base structure works.
  • Keep JavaScript hooks and visual classes in the chunk layer, not inside resource titles.

The donor topic is useful because it captures the real pain point: designers hand over a static nested menu, and developers need a maintainable way to generate the same structure from the resource tree.

Newer post

Resolving External Catalog Aliases Before Evolution CMS Routing Runs

A routing strategy for product pages that live in an external database but still need to be displayed inside Evolution CMS.

Older post

Tuning AjaxSearch for a Product Catalog in Evolution CMS

How to keep AjaxSearch focused on real products instead of container documents and make search behavior more useful for storefront users.