Use menu providers

The building blocks of the navigation are menu providers and menu items. A menu provider provides an enumeration of menu items which are organized in a tree according to their menu path. Optimizely Content Management System (CMS) contains a menu provider that looks at [MenuItem] attributes and provides them as menu items.

You can extend the standard menu by implementing a menu provider as an attribute alternative. The menu provider returns menu items that are correctly localized. To use a menu provider, implement the IMenuProvider interface, decorate it with the [MenuProvider] attribute, and make it part of a registered shell module.

You can add menu sections and sub-menu items such as menu sections, drop-downs, URLs, and pop-up menu items. Each menu item defines a path which determines its location in the menu hierarchy. For example, a URL menu item with path /global/cms/myMenu is placed in the CMS section of the menu (which has the path /global/cms). To add siblings to the CMS, place the menu item beneath global instead; for example /global/mymodule.

Types:

Example:

A menu provider returns localized menu items.

A menu provider can specify AuthorizationPolicy for each menu item, that controls which policy must apply for the menu item to be available. You can also defer permission filtering to the menu item by setting the IsAvailable delegate to a method that checks access for the user provided with the HttpContext parameter.

Menu items flow from the providers into a hierarchical model rendered into HTML.

You can extend the menu by configuring NavigationOptions through code or appSettings.json. The following sample creates a menu item on the uppermost level. There needs to be an endpoint that serves the view for the first menu item within because it is selected by default. The view should render the menu using the @Html.CreatePlatformNavigationMenu() and @Html.ApplyPlatformNavigation().

The following sample shows how to render the view in the view returned by the endpoint matching a particular menu item.

You can also render the menu items within the Add-ons section like in the following sample. In this sample there also needs to be an endpoint that monitors the route and serves the correct View.

You cannot provide icons for menu items positioned below the Add-ons header.