Hi,
No matter how you build and organize the content tree, you'll still need xslt to parse the content tree and get the right navigation! No technical issues here I suppose, just depends on how the content editors are going to use the navigation in the admin backend! Just ask what makes more sense, and build the content tree to their needs. Navigation comes second! you'll always find that fine piece of xslt that does the trick (Can become complex, but it's almost always do-able). Avoid creating duplicating content in the admin section (that is, as you said, creating two navigation structures), just create a single navigation, and use xslt to create both left- and top navigation. If you need help with this, just ask here in the forum.
Quote:My idea is to create the node QUOTES at the top level of the content and to create in this node all the nodes of the quotations. Is this a good approach or this quotations are too much
It's certainly a good approach. Just create two document types, one used as a container ('Quotes') and another one for a single 'Quote'.
Hiding certain pages from navigation can be easily accomplished. Just add an extra general property called Hide page (alias = 'umbracoNaviHide'). In your xslt, you can check for the value of this property to include/exclude nodes from navigation. Have a search here for umbracoNaviHide on the forum, you'll get lots of pointers.
[EDIT] And Dan has already given some nice xslt and screenshots! Great![/EDIT]
Good luck!
Regards,
/Dirk
level 1 certified - umbraco blog at
netaddicts.be - working on an integrated forum4umbraco