Drewster, you’re quite right, it is extremely complicated and hard to work out. Some of it’s because there’s simply a hell of a lot you can do with Wayfinder, and some of it is because the documentation isn’t massively clear. One thing I did was to mock up a comprehensive-as-I-possibly-could navigation, creating chunks wherever they could be created, classes wherever they could be created, and so on. I didn’t use real html. I did things like:
<this is the rowTpl[+wf.id+][+wf.classes+]><a href="[+wf.link+]" title="[+wf.title+]" [+wf.attributes+]>[+wf.linktext+]</a>[+wf.wrapper+]</this is the rowTpl>
for the &rowTpl, and
and so on, until I’d defined everything I could. Then I printed out the resulting code and stared at it until I figured out how it fitted together. It didn’t tell me everything I needed to know, but it gave me some clues. When I came to create real navigation, I figured out the rest of it.