Geoff, Thanks for the reply!
Assuming I give each dmHTML page a corresponding dmNavigation node, and also assuming I only want certain dmNavigation nodes to display in my nav menu, does that mean I can't use the core genericNav webskin, as it seems to display all dmNavigation nodes? Or is there some way to flag certain dmNavigation nodes to not display in the resulting nav menu? If I can't use the core genericNav webskin, can you point me in the right direction for "revealing links in your presentation layer as you want them"? My guess would be copying the core genericNav webskin to my project and modifying to suit. But this can't be correct, as I would still be faced with the problem of how I flag dmNavigation nodes for nav menu display (i.e. how would my customNav webskin know which nodes to display?). This seems such a fundamental issue I can't help but feel I've missed something obvious. I am also considering writing up some tutorials / howtos for the wiki once I get this sorted myself, so hopefully your efforts in helping me won't be wasted on just me. -Justin On Aug 9, 9:54 am, modius <[EMAIL PROTECTED]> wrote: > Generally every page should have its own corresponding navigation > folder, ie. one folder per page. The original design for multiple > pages under a single folder was for multi-page features, similar to > what you might see on a news site for longer articles. Even though you > do not want these elements in your navigation structures, you'd be > better off sticking to one folder/one page and just revealing links in > your presentation layer as you want them, rather than sacrificing the > utility of having the page attached to a folder. > > If you haven't discovered it already, try your hand at the Quick Site > Builder (Content > Content Utilities) to play with building > information hierarchies in your tree. Then try right mouse clicking > on the tree and seeing what can be done with a little cut/copy and > paste. > > All the best, > > -- geoffhttp://www.daemon.com.au/ > > On Aug 9, 8:02 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > I'm currently setting up a FarCry site for the first time and I have a > > few questions (that will surely grow in number as I work through the > > site). First, a hopefully basic question. I am creating the dmHTML > > pages and dmNavigation nodes and I don't completely understand the > > role of the dmNavigation nodes. I know that a side-effect of creating > > dmNavigation nodes is that they show up as nodes in a nav menu, > > whereas dmHTML pages do not. So the only criteria I have at this > > point to determine whether to create a dmNavigation node for each page > > is whether I want the the page to show up in a nav menu. > > > Here is an example. The site I am working on has the following pages: > > - Home > > - About Us > > - Terms of Use > > - Privacy Policy > > - Browse Companies (listing of registered companies) > > - Browse Products (listing of posted products) > > > The navigation menu should only contain the following nodes: > > - Companies > > - Products > > > So my first attempt at create the site structure was (I hope this > > comes through okay): > > > o- Root > > | > > o- Home (Nav) > > | > > |- Home > > |- About Us > > |- Terms of Use > > |- Privacy Policy > > o- Companies (Nav) > > | | > > | |- Browse Companies > > | > > o- Products (Nav) > > | > > |- Browse Products > > > This worked when I created my menu. However, I feel like I'm missing > > something about dmNavigation nodes (from the tutorials I have read and > > watched). Does this raise any red lights with anyone so far? > > > Thanks in advance for any replies. > > > -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 -~----------~----~----~----~------~----~------~--~---
