Issue link: https://epubs.iltanet.org/i/37773
“When users access your public website, SharePoint will look to their browsers’ accepted language to determine which site variation they should see.” hierarchy for content propagation is managed through the creation of variation labels. Each variation label is associated with a locale and is generally given a name based on the culture-region format. For example, if your primary site is English (U.S.), you would name your source variation label as “en-US.” If you also wanted to create English (U.K) and French (France) sites, you would respectively create variation labels of “en-GB” and “fr-FR.” When configuring variations, you must choose whether content published on your source site should be automatically or manually propagated to your destination sites. Your firm’s specific use cases for content authoring and translation will determine which option to enable. If your destination sites are one-to-one translations of content from your source site, or if the majority of 42 Portal Platforms ILTA White Paper content from your source site should be translated to your destination sites, then it probably makes sense to enable automatic propagation of content. If your destination sites tend to contain highly localized content with only a small subset of content from the source site, then it may make sense to use manual propagation, or to not use variations at all to manage your content. To illustrate how content propagation works, let’s assume an author creates a news item on the source English (U.S.) site. That news item may go through an approval process, based on a firm’s business rules. Once approved, if automatic propagation of content has been chosen, that news item will be created as a draft in English (U.K) and French (France) destination sites. The respective content authors for the destination sites will be notified that there is a new piece of content ready for translation.