...
As can be seen, the default implementation is provided by the ListModel class. Since Admin Nav is designed to be pluggable, any user interface could be provided to present these links. For example, a hierarchically organized tree could be used to group related links by administrative area like channel administration versus internal cache administration. Since the implementation defines how the parameter map is used it could also define prefixes to map keys that indicated the parameter was not to be used as a query parameter but defined what portion of the tree the link should be placed under. List
#List Model's static links file
...
In addition to accepting dynamic registrations of links, the reference implementation, ListModel, also looks for links defined statically via a configuration file in the properties directory. The name of the file is adminNav.xml. Upon instantiation, ListModel uses two other utility classes provided with AdminNav to load these statically defined links. And instance of ResourceBundleResolver is instantiated pointed at '/properties/adminNav'. This provides an instance of ILabelResolver that will look for resource bundles with that base name for the current locale of the user.
...