I do the same thing. I have Root --> Home for my main nav but I have a secondary nav root (usually called "Secondary Nav") also under root (Root --> Secondary Nav). I've also set up a dual site tree having 2 nodes under home (tree 1 & tree 2). Make sure there is a nav alias and refresh your application scope and you'll be able to access those through application.navid.your_nav_alias. Pass that to genericNav and voila
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, August 09, 2007 4:54 AM To: farcry-dev Subject: [farcry-dev] Re: Site Setup Questions: Navigation Structure I just thought of another option: create the dmNavigation / dmHTML for the pages that we don't want to display in the nav menu outside of the Home node: o- Root | o- Home (Nav) | | | |- Home | | | o- Companies (Nav) | | | | | |- Browse Companies | | | o- Products (Nav) | | | |- Browse Products | o- About Us (Nav) | | | |- About Us | o- Terms of Use (Nav) | | | |- Terms of Use | o- Privacy Policy (Nav) | | | |- Privacy Policy Then we can point genericNav at the Home dmNavigation node. Is this a feasible solution? How do others handle this? -Justin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
