by RamonS on Fri Sep 23, 2016 5:35 am
From what I read in discussions on this forum, top nav is not working out for projects with many levels (as you already found out). I do not know of a direct solution, other than flattening the structure or not using top nav. I suggest you look into flattening of the structure, eight levels deep is a lot for any navigation, menu, or tree.
It all depends on how your help is built. Maybe applying a DITA approach might help. In case you are not familiar with that, in the DITA mindset topics are categorized into three groups
-Task topics: how do I do something...typically step by step instructions for a process or feature
- Concept topics: what is this about...that would be introductory topics that describe an area, page, or feature in the application
- Reference topics: anything else that is not a task or concept, such as lookup lists, explanations of error messages, sample report output, etc
The concept topics lend themselves well to be associated with main entries (means a book in the ToC), with task and reference topics associated with that area below. That should work well if there is not that much interaction between the various areas in the application.
I have also seen structures where task, concept, and reference are the only three top level entries (with better names, such as "How do I....?" for tasks) and then all the applicable topics below with maybe an extra level to give some better orientation as to which topics belong to what area or feature.
With that in place you should be able to reduce the levels down to four at most, even if it ends up being five for very feature rich, complex areas. That will still be three levels less than what you have now and might just make top nav a suitable option again.