Technical / Architecture Question
How would you structure shared content across multiple channels in Xperience by Kentico?
We have hundreds of user profile pages with real URL slugs accessible on public sites. Each channel must render the profile page template, so the content should come from a single source of truth. However, each channel also needs its own aliases for the same profiles.
My current idea:
- Create a shared content type in the Content Hub for user profiles.
- In each channel, create profile pages that reference the shared content via a selector.
- The challenge: this duplicates management effort. For example, deleting a profile in the hub requires deleting it in every channel.
- It gets more complex as we plan to add a third channel, which will also need to display the same profiles with its own templates and slugs.
Question:
What architecture would you recommend to avoid duplication while keeping profiles reusable across channels with unique aliases and templates?
Environment
Xperience by Kentico version: [31.7.0]
.NET version: [10]
Execution environment: [Private cloud (Azure/AWS/Virtual machine)]