There are multiple view dimensions and levels available. We need to work out which ones we wire up where, to give the user a consistent and intuitive navigation experience that allows them access to the power of our navigation paradigm without exposing them to the complexity.

I need to start with writing down a map of what is possible.

The existing nav pages are a good start, but the level of complexity is going to high. We will be able to generate a dizzying array of possible views. We need to work out how the user accesses the following:

* proximal dimensions (next concern for this technology)
* a view rotation (switching from traversing mod_cluster topics to viewing configuration topics for all components)
* a narrower focus (descending). eg: going from a view of Hibernate Developer Tasks to Hibernate Web Application Developer tasks.
* ascending. do they go up one, or do we give them access to a root node?
* root nodes: technology by concern; concern by technology; concerns for this technology; top-level node
* next task in a sequence (related through a Task Overview)
* related topics

Once we do https://bugzilla.redhat.com/show_bug.cgi?id=704154 we will have literally thousands of navigation pages. The relationships above (plus maybe a few others that I haven't thought of) are the natural relationships between the topic that the user is looking at and proximal topics and navigation dimensions. So there is a constrained set of links. Even so, that's quite a few. We need to work out what the majority use cases are, focus on those, and also use visual design in the layout of the links to assist the user in intuitively accessing the functionality of the site.