Interesting idea. Let me try to make the case for using Wayfinder as a tool to help you do what you want.
Quote from: efarley at Feb 24, 2010, 12:02 PM
Let me try and make a use case to explain how I would like to have everything work.
I build a site for a client and hand it off to them. This site has a TopMenu consisting of Home, About Us, Contact Us. Now the user decides they would like to change About Us to say Company Profile while maintaining the current link, then they also want to add a external link to www.modxcms.com after contact us.
If you’re using Wayfinder, the user just changes the Menu Title of the "About Us" page to "Company Profile" and creates a weblink to www.modxcms.com.
Then they also decide to set up a tutorials page and on the left they want to put a menu for resources they used. They can then go and define a resources menu and add the links they want to it. Finally they should be able to go to the tutorials page and say this page uses the resources menu for a left menu.
If the tutorials page template has a spot for a Wayfinder menu showing all children, all the user has to do it create the resources under the tutorials page (or put weblinks to them there). Admittedly, the user doesn’t have control over the placement and style of the menu, but you could let the user choose from several templates and set a TV for the menu style. Wayfinder is completely agnostic with respect to the placement and styling of the menu so your case here isn’t really a case against using Wayfinder.
Having my menus work this way also makes it easier to set up and maintain permission based menu such as an Admin has Edit and view available in their menu but a stander user can only view. I can make a call to a AdminTopMenu instead of TopMenu if you’re logged in with admin rights to give you more options.
It’s very easy to show a different Wayfinder menu to members of different user groups. One menu can use a Tpl chunk that presents the resource menu titles as links, another can show them as text.
BTW, the permission system in Revolution is much more granular and separates view, list, and edit permissions so what you want would be automatic.
I think I understand what you’re trying to do. IMO, It will be much more work than using Wayfinder and will need more user support and training. It does sound fun to build, however.
Since Wayfinder bases the menu on the site tree structure, users don’t need to know Wayfinder exists to change the menu. They just need to know how to reorganize the site tree and change the Menu Titles of resources. You could create a menu tool to edit the Menu Title and Show In Menu checkbox for all published documents and provide drag-and-drop reorganization of the resources tree (already there in Revolution). That would be really useful for a lot of people and maybe as much fun.
I can see that there might, theoretically, be situations where you don’t want the menu to reflect the site tree in any way, but I suspect that in practice, that usually means that the site structure hasn’t been organized properly.
just my $.02