Background
DotNetNuke has a long history of core
Navigation Providers from the early days of Solpart (long since obsoleted) to asp2menu. Many of these used tables/javascript which was acceptable at the time, but as the needs of websites changed, a menu that supported non-table based layouts and semantic markup. To support this the DNNMenu was introduced in 3.3/4.3
builds. However the initial versions of this menu contained embedded styling - with the 5.1.4 DotNetNuke release, DNNMenu version 2.0 was introduced which removed all inline styling, making this menu both flexible and powerful.
Note: in DotNetNuke 6.0 the
DDRMenu was introduced and is the new recommended navigation provider.
How to tell if you're using DNNMenu
DotNetNuke defines the default navigation provider in the web.config. If DNNMenu is the default then you will see a line such as :
<navigationControl defaultProvider="DNNMenuNavigationProvider">
However this is not a guarantee that the DNNMenu is being used - this is the value used if the navigation control does not specify a provider e.g.
<dnn:Nav runat="server" id="dnnNav" />
Similarly a skin may choose to override the web.config value with a specified provider name e.g.
<dnn:Nav runat="server" id="dnnNav" ProviderName="DNNMenuNavigationProvider" />
Configuration
Once your sure your skin is using DNNMenu you will want to configure it.
The primary source for this information is the excellent video on Jon Hennings
blog .
Another popular resource is this
site which has an excellent online editor that allows you to set all the values needed.
Additional references