• Documentation
  InstallationUsing the Kentico interfaceDeveloping websitesConfiguring KenticoManaging usersSecuring websitesDeploying websitesManaging website contentMultilingual websitesMacro expressionsExternal utilitiesIntegrating 3rd party systemsCustom developmentE-commerce featuresOn-line marketing featuresIntranet featuresCommunity featuresRunning Kentico on Microsoft AzureUsing Amazon web services with KenticoReferencesRelease notes - Kentico 8 versions
• Tutorial
  Using the Kentico interfaceManaging content - The basicsSite development overviewCreating pages using the portal engineWalkthrough - Creating a new site using the Portal engineCreating pages using ASPX templatesWalkthrough - Creating a new site using ASPX templates

You can choose which pages to load by configuring standard page filtering properties, such as the Path, Page types or WHERE condition. Use the Select only published and Check permissions properties to ensure that the navigation is accurate on the live site.

Please be aware of the following behavior when working with navigation components:

• Navigation components load and display data according to the navigation properties of pages.
• If the Path property is empty, navigation components load all pages on the website (equivalent to /%).
• If the Page types property is empty, navigation components load and display only CMS.MenuItem pages.

The Breadcrumbs / CMSBreadcrumbs component is an exception, and displays all page types by default.

• When writing ORDER BY expressions for navigation components that display pages in a tree structure, the root of the page tree (or sub-tree) must be first in the resulting order. Always start your Order By clauses with the NodeLevel column, for example: NodeLevel, NodeOrder
• Navigation data sources always load a default set of page columns (required to correctly display pages in menus). The Columns property allows you to add extra columns if your menu needs data from a field that is not included in the defaults. To find a full list of the default navigation columns, use the SQL queries debuggingtool and inspect the query performed by your navigation component.

Example - Creating a menu

The following example demonstrates how to create a basic two-level menu using the CSS List menu web part.

Adding the menu web part

1. Open your website in the Pages application.

2. Create a new page.

3. Open the new page's Properties -> Template tab.

4. Select None in the Page nesting section and click Save.

   • Disabling page nesting is not a required step for creating menus, but allows you to have a completely blank page for the purposes of the example.

5. Switch to the Design tab.

6. Add theCSS List menuweb part to the page.

7. Configure the web part's properties:

   • Content filter -> Maximum nesting level: 2 (ensures that the menu only loads and displays the first two levels of the website's content tree)
   • HTML Envelope -> Content before: <div className="SimpleMenu">
   • HTML Envelope -> Content after: </div>

8. Click OK.

The web part displays an unstyled list of page links. Pages on the second level in the site's content tree appear in sub-lists under the parent pages.

Defining CSS styles

Implement the design of the menu using CSS stylesheets. You can either assign a separate stylesheet to the page (shown in the example) or use the website's main stylesheet.

1. Open the page's Properties -> General tab.

2. Uncheck the Inherit box next to the CSS stylesheet property.

3. Click New.

4. Type a Display name for the stylesheet and enter the following CSS code:

   CSS

   Copy

   .SimpleMenu UL {
     Border: #c2c2c2 1px solid;
     Float: left;
     Font-size: 12px;
     Font-family: Arial;
     Background: #e2e2e2;
     Padding: 0px;
     Margin: 0px;
     List-style-type: none;
   }
   
   /* Makes the first menu level horizontal */
   .SimpleMenu LI {
     Float: left;
   }
   
   .SimpleMenu A {
     Padding: 3px;
     Margin: 0px;
     Display: block;
     Width: 120px;
     Color: black;
     Text-decoration: none;
   }
   
   /* Highlights menu items on mouse-over */
   .SimpleMenu A:hover {
     Background: #808080;
     Color: white;
   }
   
   /* Hides the second menu level by default */
   .SimpleMenu UL UL {
     Display: none;
   }
   
   /* Displays the second level when hovering over an item on the first level */
   .SimpleMenu UL LI:hover UL {
     Display: block;
     Border-top: none;
     Width: 125px;
     Position: absolute; 
   }

5. Click Save.

6. Close the CSS stylesheet properties dialog.

7. Save the page to assign the new stylesheet.

You can now view the menu on the live site. The menu displays the first level horizontally, and the second level appears when hovering over menu items with child pages.

Setting navigation properties for pages

You can configure how individual pages behave and appear when displayed by menus or other navigation elements.

1. Open the Pages application.
2. Select the page in the content tree (in Edit mode).
3. Switch to the Properties -> Navigation tab.

The navigation settings apply when Kentico navigation web parts and controls display the given page.

Basic properties

Menu actions

Menu design

The menu item design properties are available in three alternatives:

• Standard design
• Mouse-over design - style used when users hover their mouse over the menu item
• Highlighted design - style applied if the page represented by the menu item is selected by the user

These values override:

• The settings of individual navigation web parts (controls) unless their Apply menu design (ApplyMenuDesign) property is disabled.
• The CSS styles defined in the page's CSS stylesheet.

Using CSS prefixes

CSS prefixes allow you to:

• Specify different styles for any level of hierarchical menus
• Place multiple menu web parts or controls of the same type on the same page and differentiate their CSS classes

You can work with CSS prefixes when using the following navigation components:

Example

The following example shows how to specify different styles for individual levels of a CMSMenu control (or Drop-down menu web part):

1. Fill in the CSSPrefix property of the web part or control with the following value: MainMenu;SubMenu;OtherLevels

   • Semicolons separate individual levels of prefixes.
   • Every prefix represents a lower level of the menu, starting from the main level (0).
   • The last defined prefix also represents all remaining sub-levels.
   • If you only wish to differentiate between CSS classes used by multiple menus on the same page, setting one prefix level is sufficient.

2. Define the following CSS classes in the page's stylesheet:

   CSS

   Copy

   /* Class applied to the entire menu component */
   .MainMenuCMSMenu
   
   /* Classes applied to the first level of the menu (level 0) */ 
   .MainMenuCMSMenuItem
   .MainMenuCMSMenuItemMouseUp
   
   /* Classes applied to the second level of the menu (level 1) */
   .SubMenuCMSMenuItem
   .SubMenuCMSMenuItemMouseUp
   
   /* Classes applied to all underlying levels of the menu (level 2 and lower sub-levels) */ 
   .OtherLevelsCMSMenuItem
   .OtherLevelsCMSMenuItemMouseUp

   Set the names of the CSS classes according to the following format: <CSS prefix> + <Class used by the menu component>

The web part/control applies the appropriate CSS classes when rendering the corresponding levels of the menu.