I have a site that has a number of FAQ (custom) objects under one nav node. The first object is a FAQ template that quries all the objects of type FAQ and generates the questions (title) and short answer (teaser) and a link to the FAQ.
Works well. Whoa, look at the time - better get packing for MXDU!! On Tue, 15 Feb 2005 14:20:27 +0000, Chris Kent <[EMAIL PROTECTED]> wrote: > Jeff Coughlin wrote: > > > > Jaci Chesnes wrote: > > > >> Chris...out of curiosity why do you try not to have multiple dmHTML's > >> under one nav node? Does it cause some kind of problem that I should be > >> aware of or is it just a preference. If it's just a preference what's > >> the reason behind it. Anything I can do to save myself hassels in the > >> long run is worth the time on the front end. > > > > > > I can't speak for Chris, but I don't like (presonal preference) to do it > > because when using dmNavigation to link to dmHTML objects, the > > dmNavigation (by default) only links to the first dmHTML object found > > underneath it. So the only way to link to other dmHTML objects is to > > link to their objectids directly. > > > > I had one client who was interested in this option though. They had > > multiple files in one dmNavigation that they wanted to rotate. > > > > Example: You have 4 files (each representing a season). Your company > > wants to "move" each file up to the top of the navigation node when it's > > corresponding season starts (works great). But when using the verity > > search it searched all of the dmHTML objects. The only workaround was > > to either edit core verity files or set the dmHTML objects to draft. > > > > This doesn't mean that having multiple dmHTML objects in a navigation > > node is bad, its just a personal preferrence (at least for me). > > > > -Jeff C. > > > > > I agree with Jeff, personal preference. > > And also keeping a one-to-one relationship between the site navigation > and the site pages is a good practice. > > So far i have not found an absolute-must-have situation to have many > dHTML's under one dmNavigation. The closest i could think of would be > where the content of the page is so long that you decide to break it > into page1, page2, page3 etc. But if this is the case, then maybe you > should review the content and create a summary page and child pages with > their own navigation nodes. > > > Chris. > > --- > You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
