Multisite Virtual Path Limitation

[bewards]

Description

With the multisite middleware and graphql edge limitation of not exposing and resolving the Sitecore Site virtual path field, is there any current strategy for having multiple SXA Sites where each site corresponds to the same host names but differnet sub-paths: site.com/siteA, site.com/siteB, and so on?

I am looking to architecting a 80+ multi-site solution in this manner by setting the virtual paths as there are many benefits to having separate sites, including from the perspective of the company's communication teams that don't cross collaborate and SXA related functionality such as site-specific module scaffolding, security, workflow, etc.

The only approach I can think of would require hosting a Rendering Host application per site where each app specifically sets the site via ENV, and then a networking layer above that handles the request start path to send the user to the appropriate rendering host.

Additional information

Is there a known timeline around supporting the virtual path that works with XP?

[Chris1415]

Hey, did I get it right that you are trying to do the following?

• Create X Sites in XMC
• Have 1 Rendering Host
• Map the X Sites to the 1 Rendering host in following way www.sitecore.com/SITEA, www.sitecore.com/SITEB, www.sitecore.com/SITEC and so on, that each site from XMC is accessible via a sub path of the actual deployed host?

If yes, I am not aware of any Roadmap Item or change we are planning to support it on the SDK side.

[bewards]

Hey Chris! Your understanding is correct. Since this isn't supported, we've created our own "site token" and branch scaffolding for "micro sites" instead, although we don't get any of the site-level SXA benefits such as role creation and so on - all of that would have to be implemented with our own "site powershell script modules".