Feasibility of Sharing a Site Across Headless Tenants in Sitecore XM Cloud

 In Sitecore XM Cloud, sharing a site across multiple headless tenants isn't supported out-of-the-box due to the isolated nature of tenants. However, there are a few alternatives depending on your specific requirements:

---

Key Points

1. SXA Shared Site:

   • SXA’s Shared Site feature allows sharing of presentation and data sources within a single tenant.
   • It does not support sharing across tenants by design, as tenants are meant to be isolated.

2. Restructuring the Tenant/Site Setup:

   • If sharing site content across brands is essential, consider restructuring your tenant and site setup to group related sites under a single tenant.
   • Example:
     • Tenant (Brand):
       • Site 1 (Microsoft)
       • Site 2 (Apple)

3. Item Cloning:

   • For specific content sharing, you can use the item cloning feature to replicate content across sites within a tenant.
   • This approach works well for small-scale content sharing.

4. Role-Based Access:

   • Within a single tenant, you can create shared folders/sites and assign specific roles to users for access control.

---

Proposed Structure Example

• Tenant A (Shared Site X):

  • Site 1
  • Site 2
  • Shared Site X

• Tenant B (Shared Sites X and Y):

  • Site 3
  • Site 4
  • Shared Site Y

• Tenant C (Shared Sites X, Y, and Z):

  • Site 5
  • Site 6
  • Shared Site Z

---

Recommendations

• If restructuring tenants isn’t feasible, use item cloning or shared folders within a single tenant.
• For better long-term scalability and fewer manual steps, align the tenant/site structure with the requirements for content sharing at the planning stage.
• If sharing is minimal, item cloning may suffice without extensive rework.

This approach should help address your team’s need for shared sites across brands while adhering to Sitecore XM Cloud’s design principles.

Sitecore XM Cloud: Custom Error Details in Content Editor (YSOD)

 Sometimes, when using the Sitecore XM Cloud Content Editor, you might encounter the Yellow Screen of Death (YSOD). This raises a common question: Can we enable custom error details to see more information about these errors?

The answer lies in modifying the web.config file. In XM Cloud, while you can adjust settings using XDT transformations, Sitecore doesn’t provide a direct option to enable custom error details specifically for the Content Editor.

To make changes:

1. Check out the Sitecore documentation on XM Cloud build configuration.
2. Use XDT transformations to adjust the relevant settings in the web.config file for your instance.

This should allow you to customize error handling and potentially show more details during troubleshooting.