There are two main ways to configure how the Experience behaves in terms of routing (deciding which view to show for which URL) and resolving the right URL to open when opening content:
- matching the path to the path defined in the views.json's path field (static routing)
For views that have a fixed path, the views.json's path field can simply be used to define the path under which a view is shown.
See Static Routing for full documentation.
Dynamic Routing offers enhanced flexibility and control over how URLs are resolved and associated with different views and content.
See Dynamic Routing for full documentation.
- URL: a full address that is shown in your browser's URL bar, e.g. https://www.purplepublish.com/experience
- Path: the part of a URL describing the exact resource/view to show (e.g. /experience) There are multiple:
- in apps, the experience runs in "hash routing mode" (e.g. purple://storefront/resource/dynamic/storefront/index.html?title_bar=false&bounces=false&force_status_bar=true#/home). In this example, the path is after the #, so /home
- on the web, the routing is path-based, so the path is directly after the domain:
- on custom domains, the path follows directly after the domain
- on testing domains (web.purplemanager.com and similar), the first segment of the path is used to identify the app and is not part of the path exposed inside the Experience.