Design & Technology July 07, 2016
Multilingual and Multisite with Magnolia
The market is becoming more and more global. Even in your own country there is a huge non-native population. Why should you not attract more visitors to your website and go for a multilingual website?
A website in just your own native language means you do not attract an important (international) audience. Previously the reasons to go for a single language website were valid, since it was hard to create and maintain multilingual websites. Not these days. Not with Magnolia.
Besides Multilanguage you should consider if one website for the broad variety of products and services you offer is fulfilling the expectation of your audience in terms of customer experience. If you search for a new TV, do you want to be bothered by offers for fridges? I guess not. Besides it’s way easier to optimize a specialized website for Google. In the Netherlands, CoolBlue is famous for this approach with websites like www.pdashop.nl and www.tvstore.nl. Is it hard to create and maintain multiple websites? Not anymore. Not since Magnolia CMS made it easy.
Magnolia & multilingual
Every language a separate CMS instance and basically every language a separated website. That’s how it was in the beginning of the internet age. Nowadays its way more advanced. Take Magnolia CMS as an example. You can easily create multilingual and multiregional websites in 1 CMS instance. You just create one maintainable site structure across all languages with one single site hierarchy.
Within Magnolia each translation is stored as a property under the same node which makes it easy to configure and maintain for authors because you don’t have to duplicate pages in order to make a new translation.
Magnolia & multisite
If you consider to create more than one website, for example microsites, product websites or campaign websites, it should be easy to maintain those different websites. Some CMS’s choose for a ‘one tree approach’, an approach with all websites and its underlying pages in one tree.
Other CMS’s choose for a ‘multiple tree approach’. In this case you have a separated website tree for every single website. Both has it advantages and disadvantages as you can see in the scheme below:
Magnolia’s Mix tree approach
With a ‘mixed approach’ Magnolia CMS uses the advantages of both approaches. With Magnolia you create one multilingual tree and multiple monolingual trees. The multilingual tree is for the main international sections of your website or websites. In this tree you will create and manage the general content.
Besides that multilingual tree you can choose to create monolingual trees for for example region specific content. An extra advantage is that your regional content managers has a separate content tree to manage, so you can choose to not allow them to change the main content.
Ofcourse, with this approach you can share templates, themes and features so you can use them in all trees and on all different websites.