My biggest gripe with Target Containers is that any pages listed within a target container do not show up correctly within in your navigation areas.
Breadcrumbs, Primary and Secondary Navigation areas should always provide the correct level of 'feedback' to the user so they know exactly where they are in the site. Making sure your project meets the needs of users browsing the site is your number 1 concern, followed closely by editors maintaing the project within the CMS. Any performance gains from using Target Containers are irrelvant if users become frustrated with using the site (due to usability issues) and never return back. Some might argue that a few 'missing' links in the navigation is no big deal.. however, if i ever come across a site where i find i difficult to find the content i want quickly, im outta there in no time.. and im pretty sure most other people would be too. On Aug 24, 6:53 pm, "Richard Hauer (5 Limes)" <[email protected]> wrote: > Do you use target containers? Yes (and no). > > As with anything this is going to come down to your requriements and > the nature of the site you are trying to render. When doing a > microsite (a site with few pages, say 10-20) and limited navigation > then I would definately go for target containers rather than Nav Mgr. > > Listen up here people: > DON'T USE NAV MANAGER IF YOU DON'T HAVE TO* > *unless you're in v10, in which case DO cause it's hard-wired into the > author experience > > Why not? Cause it adds a whole layer of per-page processing and will > wreck your performance both for publish and in SmartEdit. > And when you're not using NavMgr target containers are actually very > useful. The publication engine is optimised around their use so it > works properly when you use them properly. > > When dealing with anything other than a microsite, which almost always > have proper navigation requirements, you are bound to Nav Manager for > ease of use and managability and that means target containers are out. > > Remeber that Nav Mgr processing is expensive in terms of computation > required for publication and SmartEdit so use it sparingly, limit your > render spots, and don't use NavMgr where pre-execute will do > (definately try not to mix them otherwise each page is going to get > processed 3 times! add RDExecute and its 4 passes per page!!) > > My 2c for what its worth... > > HTH. > > Regards, > Richard Hauer > ==================== > 5 Limes Pty Limitedwww.5Limes.com.au > > On Aug 24, 11:05 am, markus giesen <[email protected]> wrote: > > > To be honest, they cause more trouble than good for me. > > I found seldom helpful and would like to know your opinion on this. > > > Do you use target containers? > > Why? Why not? > > > What is your benefit? > > > Which project requirement can only be solved using target containers > > in your opinion? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" 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/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
