Building a Purple Experience

Menus

4min

Menus are used to enable dynamic configuration of 'lists' where the users may navigate to different parts of the app or website or also to external URLs.

There are two ways to configure menus in the context of the Purple Experience:

  • App Menus aim for native Purple Apps (configured through app-menu.xml, seeStatic Routing and App menu configuration in the Purple Experience)
    • Side Menu, also configured within Experience Builder, allows overriding the app menu-XML in web.
  • Purple Cloud Menus are configured in the Hub and published to the Purple Content Cloud, thus accessible through the Menu Component, GraphQL and the Purple API

Native app menus are also displayed on websites, if no hub is configured.

We are working on deprecating app menus fully and consolidate for a single source of truth for menus.



Benefits and Limitations

App Menus

  • native app support
  • trigger native events
  • multi-language and multi-platform translation support
  • no nesting
  • Available when offline

Purple Cloud Menus

  • nested menus
  • Configurable through the hub and thus, through Journalists
  • requires internet connectivity to be safely loaded
  • Addition to App Menus - any native App must have an App Menu.