help.axcms.netAxinom Logo
Save Save Chapter Send Feedback

Navigation Structure


Navigation through content is one of the key purposes of Information Architecture.

By defining navigation structures separately from the content itself, is able to realize significant advantages. Content is available as a set of pages. A hierarchical navigation structure (or multiple structures!) can be built on top of this information.

Fig. 1 Navigation Tree and different types of navigation assignments

Fig. 1 Navigation Tree and different types of navigation assignments

Navigation hierarchy is created by th editor in the Management System. Navigation is a tree, the depth of the tree is not limited. Every navigation node has some basic properties (Name, Description, Additions - extensible by Developer). Every navigation node can have Pages (or Documents) assigned. There are two kinds of assignment possible.

A Page (Document) assigned as a Standard Page (Document) is the one which is shown to the end user when she clicks on the navigation node. A navigation node can have only one standard assignment. (A Page / Document can be assigned as standard to as many navigation nodes as needed).

Pages / Documents can be also Attached to a navigation node. Any number of Pages / Documents can be attached to a single navigation node. This kind of assignment does not have any immediate consequence. However it defines the fact that the Page / Document has a logical relation to a given node, even if does not immediately appear when clicking on this node. It can be useful for subsequent content, which is linked to the standard page. By using attached navigation node, it is possible to highlight the navigation in the right way for the user.


Fig. 2 Navigation Tree in Management System

Fig. 2 Navigation Tree in the Management System 

The appearance of the navigation in the live system is independend from its logical structure. Usually the developer creates a Navigation Control based on specific project requirements and integrates it directly to the page template. There are many possibilities of how such a control can behave and what it looks like - anywhere from a classical top- or left-menu to a JavaScript-Layered-Navigation to a fancy Silverlight navigation with animated affects.

Fig. 3 Different representations of navigation in Live System

Fig. 3 Different representations of navigation in the Live System

It is important to understand, that internally navigation is just a part of the larger concept of Categories. The Navigation tree is a subtree of the whole categories tree with a fixed root. Because of this relationship, navigation can be used for many additional tasks beyond the pure content navigation:

  • Permissions can be set and inherited via the navigation tree
  • Assignment to the navigation can be used by dynamical controls to create lists of elements (e.g. all documents attached to a particular navigation node)

As every Site has its own navigation tree, assignment to a navigation node defines which Site a given Page / Document belongs to. A list of Sites is available in the management system in the Home-menu (the leftmost item in the top menu).

The cloning feature in is a very convenient feature.  It allows the editor to clone whole navigation subtrees, including all the assigned pages and keeping all relations. This feature can save the developer time and reduce errors when creating similar navigation trees.