I have planned a multilingual site, based on SharePoint 2010 platform. I started a research in this direction. It's easy to make multilingual UI. Variation feature will help me to redirect users to the current user language.

The first problem is content translation. Variation feature can help me only with pages library of infrastructure publishing. Content deployment doesn’t allow editing (translating) the content.

The second problem is structure. Both sites must have the same structures. Then I insert some field in the list or node in navigation and must be realized in both sites.

The third problem is styling. Masterpage, xslt, css and others must be the same too.

I'm sure I can solve these problems after some time. I'm sure someone has already resolved this problem and tried to find the best practices for making multilingual SharePoint site.

1 Answer 1


Content translation is always a manual process. Once a variation has been created from a published page, it appears in the target variation as a draft, ready for manual translation.

Ensure your list schemas and navigation nodes match your requirements before creating your variation hierarchies.

Styling will always be consistent and inherit from the root level masterpage by default, though you can later change the style by breaking the masterpage inheritance at any time.

More time must be spent into your requirements and testing the source variation's structure before creation your target variations.

  • from technet.microsoft.com/en-us/library/ff628966.aspx: The variations feature does not copy other site content, such as lists or other document libraries, unlike the content deployment feature, which copies all content, including lists and other document libraries, from one site to another.
    – IAfanasov
    Jul 2, 2011 at 10:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.