multilingual websites, microsites and landing pages

Magnolia is a registered trademark owned by Magnolia International Ltd.Version 1.1

Will Paoli, Atlassian & Samuel Schmitt, Magnolia 07.03.2013 at Miami Amplify

Multilingual Websites, Microsites and Landing

Pages

1

Thursday, 7 March 2013


In the USA, about 25 millions are not native

English speakers

2



The market is global

3



Do you need a multilingual website?

4



Multilanguage & Multilingual CMS

5


Version 1.1Magnolia is a registered trademark owned by Magnolia

International Ltd.

With Magnolia's multilanguage CMS

6

Manage multilanguage and multiregional sites in a single Magnolia instanceDefine one single site structure across all languages

You only need a single site hierarchyEach translation is stored as a property under the same node

The correct language is automatically served



How One Single Tree approach works

7



International Ltd.8

www.mywebsite.com/main.html


http://www.mywebsite.com/article.html

http://www.mywebsite.com/article.html


International Ltd.9

www.mywebsite.com/fr/main.html


http://www.mywebsite.com/fr/article.html

http://www.mywebsite.com/fr/article.html


International Ltd.10

The system creates subtitle and text properties for each language.



Easy to configure

11




Define in your site definition the locales available




Selecting a language from the dropdown defines the content entry language for paragraphs and properties on the page.




Dialogs reflect the choice by displaying an identifier (en, fr, de...) next to field labels.



International Ltd.

Multilanguage with Magnolia CMS

15

Simple to create a website for many countries without duplicating pagesSimple for authors to edit pages in all languages

• Export / Import translation• Custom workflow



Multilanguage & Multisite CMS

16



International Ltd.

Multisite with Magnolia CMS

17

Separate website trees, one for each language

Share templatesShare themes




with Magnolia Modules Architecture you can decouple the templates from the content



International Ltd.

Multisite with Magnolia CMS

19

Easily create multiple sites

Reuse templates and themesShare features



One Tree vs Multiple Trees

20




One Tree Multiple Trees

Less pages to manage More pages to manage

No language specific content Language specific content

No duplicated content Duplicated content

System serving correct language Custom logic

No language specific URL Language specific URL



Less and less sites have separate trees or all content translated. More and more are using a mixed approach! Jan Haderka / Magnolia Philosopher, 2013.

22



Mixed Tree Approach

23



International Ltd.

Mixed Tree Approach

24

Mix of trees where • one tree is multilingual • all others are monolingual

Multilingual tree for the main international sectionsFor each region or language create a monolingual tree



How does the Mixed Tree Approach work?

25



It takes advantage of both approaches

26



Main tree

27




Main is configured for 3 languages. It follows the One Single Tree approach.



And the other pages?

29



Microsites and Landing pages

30



International Ltd.

Microsite

31

Is an individual page or a set of pages

Has its own domain or subdomainAdds a specialized group of information

• Language specific content




US Micro site has its own configuration, own domain and share templates and theme with the main site.



International Ltd.

Landing page

33

Is a single web page

In the context of multilanguage website• has it’s own domain finishing in .fr, .de, etc. • is where a visitor lands when he comes from a search

engine




www.mysite.fr redirects to site /fr


http://www.mysite.fr

http://www.mysite.fr


International Ltd.

Bridge between main site and the others

35

Navigation must be seamless• Jump from one site to the other and stay in your favorite

language

Use Magnolia standard features• Site definition, domain mapping• Virtual URI mapping

Extend Magnolia• Create custom areas or components• Filter chain



Stop with the theory!

36



Is it really possible to implement a successful Multilanguage website?

37



¡SÍ, Claro!

38



International Ltd.

Agenda

39

Demo of atlassian.com

Our first approach to translation

The translation workflow we use

Examples of the single tree approach and where we stray from it


49

English

Spanish

FrenchGerman

Japanese


International Ltd.

Bienvenido a atlassian.com

40



Quick Demo of WAC(Www.Atlassian.Com)

41


http://Www.Atlassian.Com

http://Www.Atlassian.Com


International Ltd.

How we got here

42

Website Redesign, and Implementation of Magnolia CMS

We decided we wanted to launch with Spanish, German and Japanese translations as well

Instead of trying to translate the entire site, we started out by concentrating on translating the most critical paths.

Our initial effort was done by exporting strings and sending them to a translation service



International Ltd.

How we got here

43

Export strings to SpreadsheetSend off to professional translation serviceImporting them back into magnolia



International Ltd.

Good Start but...

44

This got us started, but we wanted it to be better

As soon as content is translated it changes

Direct translations done by a 3rd party company were for the most part good quality... as far as we knew.

Good to make sure you are communicating your ideas and not just your words



International Ltd.

Welcome “Atlassian Ambassadors”

45

Ambassadors are Atlassians that work in specific global regions to help us market our products in their countries

They also help us handle translations for the site, which is extremely valuable!

Sven Peters, Germany David Bonilla, Spain Sean Osawa, Japan



International Ltd.

Ambassador Translation Workflow

46

New version release of JIRA

In the past, we just IM’d or emailed Sven, David and Sean whenever something needed translation

We implemented a notification feature into our content publishing workflow



Demo of Notification Setup

47



International Ltd.

One Tree Approach vs Multipage

48

English

Spanish French

German

Japanese

Chinese

Russian



International Ltd.

One Tree Approach vs Multipage

Generally we use a one tree approach

Occasionally makes sense to have a completely different page if you need Localization as opposed to just language translation

49



International Ltd.

Examples of a mixed approach

50

Japanese Payment InfoJapanese Press siteLanding PagesExperts Search resultsHow to Pay Section



Demo of Japanese Payment Info

51



Demo of Japanese Press site

52



Demo of Landing Page concept

53



Demo of Experts Search results

54



Demo of How to Pay Section

55



International Ltd.

Moving forward

56

Soon we will be adding several new languages and translating our order form which currently is only in english

We are always looking for ways to improve the speed and accuracy of our translations

A promising company called Gengo which pays translators around the world to do translations and even has a Developer API which we hope to integrate into Magnolia



Gracias¿Tiene Preguntas?

57



Thanks!William Paoli

[email protected]


mailto:[email protected]

mailto:[email protected]

multilingual websites, microsites and landing pages

Technology