SharePoint in general supports a wide range of languages. However, it is not immediately obvious how to set this up, configure it and what automation you can use to take advantage of the modern Communication Sites features.
SharePoint Online has supported Welsh since 2014, which has in the past enabled us to create bi-lingual intranets using SharePoint Publishing Site features. With this, you can create variations from a source language to choose to build copies of your site or Intranet in the language you prefer.
There are challenges with this approach:
- Out of the box SharePoint isn’t enough on its own, so you are highly like to go down the customisation route. In modern sites, most are now designed for high quality visual presentation, mobile friendly, accessible and easy to use. This rich feature set is not part of the publishing infrastructure, you will have to build these yourself.
- The variation system in SharePoint is quite sensitive and prone to issues, it is not always successful that pages and sites are copied properly.
- In SharePoint Online, it is not recommended to modify master pages, as the service continually evolves with high frequency releases Microsoft cannot guarantee that your customisation will not break.
- The editing experience for staff is clunky and far from simple to use.
So for some updates…
Good bye Machine Translation Services
I have received, via the Office 365 message centre, notification of the deprecation of the Variation Labels and the Machine Translation service for Classic Publishing Sites in SharePoint Online. It is quite a surprising, major change and it certainly put a big nail in the coffin for deciding whether to go with classic SharePoint Publishing Sites for a new Intranet.
So hello Communication Sites….
Communication sites are the newest feature in SharePoint that provides: responsive, mobile support, beautiful design, accessible, new set of web parts and SharePoint Framework for client side development. As a result, Microsoft are investing heavily in this new feature with a range of new enhancements coming soon.
Whilst this is a welcomed set of features to the SharePoint world, there are some gaps:
- SharePoint Online still supports multiple languages but does not provide the user interface to create them.
- It is not obvious or even well documented how Communication sites can be setup for multi-lingual scenarios.
- If you decided to use Communication Sites, how would it work? what kinds of customisation would you need? and what you might need to get started?
In the post series…
I will be looking to provide some answers to the above questions, some suggested configurations and processes. Welsh will be the example of language to translate to, from English pages. Our client base are primarily Welsh public sector bodies at the moment and it is a requirement when building SharePoint solutions and Intranets to provide support for both English and Welsh languages as part of the Welsh Language Standards.
- Create Communication Sites with a specific primary language using PnP PowerShell
- Create Communication Sites with a specific primary language using the User Interface
- Enable your SharePoint Start Page for language preferences
- Updating the site list of supported languages
- User preferences and what effects language presentation
- Approaches to architecting multi-lingual Intranet with communication sites
- Using Microsoft Flow to replicate multi-lingual Communication Site pages in other languages
- Using Microsoft Flow for translation of Communication Site pages
We will continue to build this list as new developments or approaches come to fruition.
Note: In this post series, I am using Welsh translated from Microsoft Bing/Translator Text API, I don’t speak Welsh so I rely on the accuracy of the translator services. If you discover some Welsh terms that are inaccurate or offensive, please let me know immediately by posting a comment or DM via Twitter and I will correct the content. Thank you.
I hope you are as excited about this series as I am… watch this space!