AEM Globalization Platofrm by Anubhav Jain

AEM Globalization Platform Anubhav Jain, Adobe

• @anubhav Jain • Technical Architect for Globalization

Tools Platform at Adobe

Localize – Why?

Why Localization?

• Maximum revenue from global operations and cross-border sales

• Top 10 languages represent 82% of the

world’s internet users or ~4.4b people and growing

Localization is coming your way!

Adobe Help and Learning

Adobe Help and Learning

Adobe Help and Learning : Introduction

• Adobe Help and Learning –

http://helpx.adobe.com

• Powered by AEM 5.6

• Hosts ~70,000 pages of content - Learning

tutorials, product documentation, support page and rich

Adobe TV videos

• Localized in 37 locales

• Global dedicated authoring, production team

and a centralized globalization team

Localize it

Localization Goals

Localize articles and images

Control and flexibility to define what gets translated and what doesn’t

Publishing of localized assets

Easy tracking of localization projects and their status

High performance and scalability

अनवुाद Hindi word meaning TRANSLATION – Spelled as ANUVAAD in English

Help Localization Ecosystem

English AEM WorldServer (GMS) Middleware

Loc AEM

Preview AEM

Publish AEM

Anuvaad

Publishing environment (helpx.stage.adobe.com)

User Workflow Internationalization Program Manager (IPM)

Localization Dashboard

14

Personalization – IPM only see his products

User can define custom suffix

Auto identification of ready to be localized content

Initiate Handoff

Auto populate locale list

15

Add More Assets

16

Hand Off History

17

Hand Off Details

User Workflow Translators

19

Auto project creation and assignment

20

Translation Step

Text translation

Image localization

21

In-context preview

22

Translation completion

Review translations

Complete Project in

WS

Auto impot in Anuvaad

Auto published to stage

Internationalize Components

Internationalize Components

• One time translation of strings in components

i18n L10n

One time translation strings of in components

Identify one time translation strings in components

One time translation strings of in components • Identify and externalize strings • Anuvaad has built in workflow to manage its translation – For any component, just select it

and send it for localization • Alternatively, use CQ5 Translator OOTB

Internationalize Components

• One time translation of strings in components

• L10n Components

i18n L10n

L10n Components

Identify opportunities for L10n

Internationalize Components • One time translation of strings in components

• L10n Components

• One time translation of static components – Menu, Header and footer

• Design templates

• CSS Overrides per language

• Special care for RTL languages Arabic and Hebrew – Use of mirror

property

• Multilingual SEO

• Localize tags

• Localize sitemap

i18n L10n

Advantages

• Saves $$$

• Standardization and consistent

translation

• Translation memory

• Automated – No human error

Dynamic components

Dynamic component - Introduction • Introduction

• Aggregator components • Fetch content from one page and show it on another page • Heavily used and can be commonly found in AEM implementations

• Challenges • Pose a challenge for localization, as traditionally localization happens at a page level • Generate consistent preview • Pose publishing challenges, so that if any asset is changing, identify all components

which refers to it and re-publish them • Ensure consistent translations across referring and referred pages

Dynamic component – Topic browsing

Dynamic component – Topic index

Dynamic component – help article

Dynamic component • Introduction

• Aggregator components • Fetch content from one page and show it on another page • Heavily used and can be commonly found in AEM implementations

• Challenges • Pose a challenge for localization, as traditionally localization happens at a page

level • Generate consistent preview • Pose publishing challenges, so that if any asset is changing, identify all

components which refers to it and re-publish them • Ensure consistent translations across referring and referred pages

Dynamic component – Solution

• Identify translatable text and send it for translation

• Filter localizable text and auto localize it

• For preview request, generate preview for all affected assets – Referred and referring page :

Ex: In case of a topic index page, generate preview for topic index and affected using/help

articles

• On completion, auto import all affected assets and re-fresh dispatcher cache for all affected

assets

• Doing above manually is error prone and impossible, Anuvaad has built in intelligent peace of

code to configure above and then do required publishing

Intelligent Publisher External Interface

UX (Coral UI, Jquery, Ajax)

GMS Adapter (Apache Sling)

Legacy content importer

Custom Replication

Internationalized Components

Dispatcher

PDF Packager *

ANUVAAD Core

Localization Tree, Translation Jobs,

GMS Metadata

CRX Repository

Globalization Workflow (Based on AEM W/F engine)

Diff Generator *

Payload Generator

(XLIFF, ITS*)

Rules Engine

Image Handler

Notification Service

Locale Service MSM *

Job Manager

AEM Core

ANUVAAD – Technical Architecture

ANUVAAD Success

• Globalized content available in AEM

• Reduce time to market

• Cost reduction

• Reduced human effort

• More robust and less scope of error because of

automation

• System are stable and asset lifecycle is traceable

Multilingual DAM

Multilingual DAM

Rich multimedia assets are integral part of content residing in AEM

Multilingual DAM : Scene 7

Multilingual DAM : Best practices

• Use Adobe Scene 7 where possible, Saves $$$

• Tag images with appropriate meta data

• Separate folders

• Enhancement planned in ANUVAAD

AEM Globalization – Key Ingredients

Site structure

Rich Localization workflows

Publishing strategy

i18n and L10n components

Internationalize images/videos

Localize sitemap

Localize tags

Traceability

Analytics

Thank You Contact : anubjain@adobe.com

Q & A