Blog Sections Open

Using Wayfinder When Your Menu Markup Must Match a Fixed HTML Design

Wayfinder works best when you let it own the navigation markup, but fixed design HTML often means you need a custom rowtpl and outertpl strategy.

One of the most common Wayfinder questions is not about data, but about markup. A project already has a precise HTML menu design, and the default Wayfinder output does not match it.

The Core Tension

Wayfinder naturally produces a structured list. Designers, meanwhile, often hand over bespoke wrappers, spans, and active-state markup that only partially resembles a normal list.

The Practical Solution

Instead of fighting the snippet output directly in one giant template, split the problem:

  • use outerTpl to control the wrapper
  • use rowTpl, rowHereTpl, and related templates for item states
  • model the active branch explicitly instead of post-processing random HTML

Why This Matters

The old discussion was really about using Wayfinder as a structured renderer rather than as a magic HTML copier. Once you accept that, the menu becomes much easier to adapt cleanly.

Newer post

Using MultiPhotos to Link to a Page Instead of the Original Full-Size Image

How to rethink MultiPhotos output when thumbnails should lead to resource pages instead of opening the original large image file.

Older post

Reordering Tabs in the Evolution CMS Manager with ManagerManager

How ManagerManager-style tweaks can change the tab order in the manager when the default editing layout no longer matches editor priorities.