Menus

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, see static routing docid\ yvk2ekejex9kmanjphtkz and app menu xml docid\ nxi0s2kws4 m2o0vdlc31 ) 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 action urls and deep linking docid 4cqfqcai7gu13bn rilws 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