Navigation

System

Assuming the system manages a site with a typical assortment of flyout menus, and most of the people contributing content are non technical (the content is generally entered into a template), what is the best way to let users add records to the navigation and control where they appear? What are some of the solutions people are addressing this issue with, and how well do they work?

Kim

NOTE: I'm fairly new to TS and have worked some with the various modules. We're in the process of doing an initial stab at setting up TS for authors to eventually use to maintain their content. I apologize in advance if this was already answered in a previos thread, I did search and browse the forums, but couldn't find anything.

Along the same lines as the above post, we're wondering what strategies others have in regards to managing resource or shared files (e.g. images, include files like navigation, footer) used in entire site and actual content. Are the responsibilities split between authors for actual content and editors or admins for resource files?

Secondly, what is the method used to provide a central access point to all elements of a page rather than an author or editor going to each DCR for editing and then only previewing the changes for that 1 element vs. the entire page? For example, we are currently using the method of a DCT/TPL per element and referencing them as include files in the main ASP page for the content. However, for any edits an author must go to each element's generated file and preview only that element and then go to the actual ASP page to see it in context. Is this the way to go or is there a better way, hopefully being more efficient and easier for the authors who have to maintain the content and shared elements?