Each site is going to be mapped to a content path in Pages.

Since we cannot ensure load order in registry, each site must uniquely match the content.

If multiple sites match same pattern -> first matching site wins.

Check if MGNLSITE-131 is done. When it is, then this should be possible!
Just verify that it is works and document how.

Note:

On SaaS we want to map by the content path in Pages rather than just by domain - because different domains might not be configured for the different sites. This applies to development and to production. Customers may just be using the magnolia-cloud.com domain. Our main use case currently is for the authors who are logged into magnolia-cloud.com that the Page Editor loads the correct SPA based on the 'baseUrll' and 'routeTemplate' on the site configuration.