I am considering using the new Sitecore 6.4 cloning features to help reuse components and content across multiple sites and multiple language solutions.
The main idea is to create a central repository of content in Sitecore (possibly in several languages), which can then be cloned to provide regional sites, each of which has its own choice of supported languages. The idea of this is to allow regions to easily replicate and own required content. With cloning, they will be able to edit the data where it is required without affecting the source data, ignore elements that are not relevant to them (for example, when the product was not available in their country), add new content that was completely specific to their country and translate into any regional dialects that they want to support (e.g. Swiss French: fr-CH), etc.
The main set of sites will share a significant part of the source data, although in this case most language versions occur locally.
Does anyone have experience deploying this Sitecore? What are the pitfalls?
However, after this structure has been established, an open-ended script comes into play. New sites, for example. a site for launching a product launch can be added to a Sitecore instance, and we expect them to share content, templates, presentations, etc., where they are suitable (although to a much lesser extent than the main sites).
, . "" , , ? , . , - . , , , .
Sitecore.
? , ? ?