We have a client with some interesting requirements around content and relationships which we are considering a Kentico build for.

The client has the concept of content sharing for specific languages and markets with an inheritance model. Imagine a page that has a block of content on it. This content is written for the international audience [en]. Another version of this same content is tweaked slightly for the United Kingdom [uk] audience.

Now imagine this inheritance tree:

> [en] International Audience
>>>> [uk-ie] United Kingdom and Ireland
>>>>>>>> [ie] Ireland
>>>>>>>> [uk] United Kingdom
>>>> [de] Germany
>>>> [us] United States

When a user comes to the site, their market is determined or they can pick it. When the user is browsing the site in the context of the Ireland market, they would see the international content, when browsing from the United Kingdom market they would see the tweaked content specifically for the UK market.

Basically, if you don’t have a version of the content specifically for your market, you get the version of the content that is closest to your market when searching through your parent markets.

This concept needs to be applied to any type of content throughout the entire site.

This way they client can target content to markets or groups of markets, tweak it slightly for different markets (pricing, slang) and still be able to manage the content in a sensible way.

Further to this, the market may support multiple languages, eg: German and English. A page that lists articles that are related to a tag when viewing in the context of the Germany market, may show articles from both these languages, but a weighting would be applied to surface the German articles to the top of the list as that may be set at the preferred language in that market.

The relationships and weighting model will be quite complex.

Is this possible with Kentico? How would you approach it? Or is this looking like a bespoke build.

NB: the site will also contain a lot of personalization, as users will be logged in, so performance and caching needs to be considered carefully.