Assigning Sequential Classes to Wayfinder Menu Items

If a menu template needs sequential classes, generate them in the row templates rather than rewriting every menu item by hand.

This donor case came from a static menu where every item had its own class such as mm1, mm2, and so on. The goal was to reproduce the same structure dynamically with Wayfinder.

Best Direction

The clean solution is to push the class pattern into the Wayfinder template layer. That keeps the navigation dynamic while still satisfying the CSS system the design expects.

Why It Matters

Static class numbering does not scale when editors add or reorder pages.
Menu behavior stays consistent across template changes.
The resource tree remains the source of truth instead of duplicated HTML.

Newer post

Running Two JotX Instances on One Page Without Style Collisions

How to keep multiple JotX outputs on one page from overwriting each other’s config-driven styling.

Older post

Multisite Patterns in Evolution CMS with One Shared Database

How to think about multisite setups when several sites share one Evolution CMS database and much of the content overlaps.