Whether displayed as a website menu or navigation in your mobile app, navigation builds a hierarchy in your project.If you model your navigation, content creators can manage navigation menus without developer assistance.
Choose a suitable navigation approach
Navigation is composed of content items based on a content type dedicated to navigation. Define the relationships in the navigation using a subpages element if you use Web Spotlight or with a linked items element in other cases.When modeling the navigation, decide whether to bind content to the navigation or keep them separate.
Navigation bound to content
This way, items that you link in the subpages or linked items element also hold the content. While this approach is more straightforward for understanding the concept, it isn’t suitable for omnichannel delivery.That’s why it’s more suitable for smaller projects or projects that use one way of navigation for all channels.
Navigation separate from content
If you separate navigation from content, you’re creating two items for content linked from your navigation. The first is for the content itself; the second is for a navigation item that links the first one.This way is better for larger projects prepared for omnichannel content.
Build your navigation
Create a new content type and add elements needed for your channel. In the code examples below, this type is called the Navigation item. It typically contains: