First off, C5 is the best CMS I've found and its the only CMS my boss was willing to go with after showing him a zillion CMS's.

Now onto a little user interface challenge.

I know it seemed like a good idea at the time, but the page attribute 'replace_link_with_first_in_nav', that links a menu item to the 1st child in its subnav, creates more problems than it solves.

From the perspective of a visitor, how would I know that both the menu item with the subnav, and the 1st child of the subnav actually link to the same content?

Here's an image of my 3 tiered menu where links 1 & 2 end up going to pages they don't represent, and links 2 & 3 link to the same page:
http://www.fileden.com/files/2008/3/6/1798643/menu.jpg...

Misrepresented Menu items:
'Our Products' links to the 'Gallery' page
'Gallery' links to the 'Apartments' page

Adjacent Duplicate links:
'Gallery' links to the 'Apartments' page
'Apartments' links to 'the Apartments' page

So where should menu items with subnavs link? Nowhere! There only purpose would be to open the subnav.

Could there be times that a menu item with a subnav should link to an actual page? Sure, why not, but I'd rather not have to make a landing page for every menu item with a subnav. And while linking to the 1st child of the subnav can work for a 2 tiered menu in some cases, it seems a bit arbitrary (I mean, why not link to the 2nd or 3rd item?) and the user would have no way of knowing where they were going until they got there.

That's my two cents. What solutions are other people using to deal with this interface challenge?