building a multilingual & multi-country e-commerce site with drupal 7 @ nyc camp 2014

Post on 25-May-2015

2.122 Views

Category:

Internet

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

Building a multilingual & multi-country e-commerce site with Drupal 7

TRANSCRIPT

MULTINATIONAL & MULTILINGUAL

REUSABLE E-COMMERCE

PLATFORMCASE STUDY

Maxime Topolov, @mtopolov CTO & Co-Founder of @Adyax

Arthur Murauskas, Associate Director & Drupal Architect @Adyax

OBJECTIVES

http://www.guerlain.com/int/en-int

http://www.makeupforever.com/us/en-us

An e-commerce site connected to SAP with rich editorial content, managing multiple countries and languages, where each country is independent, where the content must be validated by France

except some...

Fluid front-end, that must work with IE6...

Guerlain

Make Up For EverAn e-commerce ready site that will be connected to Biz-Talk with rich editorial content, managing multiple countries and languages, where each country is independent, where the content must be validated by France

easy, right?

Full responsive with IE7 supportLOTS of huge HD images

KEY NUMBERS

2,500

1625

2ERP, INCLUDING SAP

COUNTRIES, INCLUDING CHINA

LANGUAGES, INCLUDING JAPANESE

PRODUCT REFERENCES

70

1215

15,000 MAN HOURS

MONTHS OF DEVELOPMENT

PEOPLE

TEMPLATES 57 CONTENT TYPES

BASIC TECHNIQUES

Main features

A single Drupal instance for all the sites.

Site launch is progressive, country by country.

Export and import of content in Excel format.

Certain sites will be e-commerce, others won’t.

Robust translation and publication workflow with alerts.

COUNTRIES & LANGUAGES

CANADA

FRANCE

SPAIN

CHINA

FR2 EN

FR3

ES

CN

SWITZERLAND FR1 IT DE

Country Country code Language Language codeInternational in EN int English en

France fr French frUS us English US en-usUK uk English UK en-uk

Middle-East me English Middle East en-meChina cn Chinese zh

Hong Kong hk Chinese zh-hkEnglish en-hk

Spain es Spain esCanada ca Canadian French fr-ca

Canadian English en-caRussia ru Russian ruKorea ko Korean krTaiwan tw Simplified Chinese zh-twJapan jp Japanese jaBrazil br Brazilian Portuguese ptItaly it Italian it

Germany ge German de

Management of languages based on several very standard Drupal modules:

Localization Client (i10n_client)

Translation Template Extractor (potx)

Entity Translation (entity_translation)

Why entity_translation?

It’s logical :)

There are no “duplicate” translation nodes

Entity translation is in D8 Core

Not all the fields should be translated

Three features were essential:

1

2

3

A ‘central’ country where all original content is first created

Possibility of copying all content of one language to another

Notification of countries in case of modification of any content in the ‘central’ country

Each country can be identified either by its domain (guerlain.co.uk), or by a URL key (guerlain.com/fr)

OK, but what is a country?

Each country has specific settings, admin users

The Domain Access module (domain) offers this feature on a platter.

Copy and pre-fill translations from source

Copy structure: menu, taxonomy, etc

EN-EN

EN-US EN-CA FR-FR

FR-BE

No revisions (btw, entity_translation do not support them). Country editors are responsible and have two versions at their disposal (draft & published)

Content workflow

When we say “content translation gets published”, it means: • Original language / Central: content is available for the

Countries' local translations; • Country local languages: content translation is available online

for the website users.

Translation workflow

Problem 1: customisation of forms (contact us, newsletter) according to countries.

Problem 2: difficulties with interface translation

Take-home message:

Building the best possible, scalable multilanguage-multicountry perfect solution, with overrides, notifications, permissions and complex workflow works fine but IS NOT USED. !

Client wants less features and a simple workflow, even if it requires more manual work from their contributors.

GEOLOCATION

Guerlain.com/es Guerlain.com/fr

CDN

VARNISH

NGNIX

Guerlain.comJS

MaxMind

IMPORT / EXPORT of content

Import of Products & SKUs with their Media

Import of Categories

Import of Stores

The Excel 97 - Excel 2003 Binary file format (BIFF8)

We tried many formats to support XLS, one that works with common PHP libs in most of cases is :

Feeds used to import data.

SKUs as well as products could have multiple photos, so we also have: !

A ZIP archive with media organized into folders product/product-ID/xxxxx.jpeg or sku/sku-ID/xxxxx.jpeg

ERP INTEGRATION

Ord

ers,

Clien

tsSKUs, Stock,

Order Status

XML SOAP

Working with SAP is not complicated, but laborious. One order can be 5000 lines of XML

We have created a tool to send an XML command to SAP, directly from the Drupal back-office !

In addition, we have put into place a log of each communication (to & from) SAP that is visible from the objects concerned (command, user, SKU)

SSL

!

Setup of the Secure Pages module !

Creation of the sub-domain wws !

SSL = User Data (Cart, My-Account)

CDN

VARNISH

NGNIX

DRUPAL

Secure Pages

Secure vs insecure / http vs https !

Start development with activating all https support. Define https urls at the very beginning! Do think about cross-site scripting and AJAX if urls differ. Secured cookies. !

Idea: start thinking secure from the beginning of every project.

SMOOTH FRONT-END

OOOOOPTIMIZATIONS

CDN

VARNISH

NGNIX

DRUPAL

ESI

BLOCS JS

STATIC.GUERLAIN.COM

MEMCACHE

ENTITY CACHE VIEWS CACHE

Never underestimate performance tuning. !

Start first Sprint by activating all performance related modules - memcache, entity-cache, adv-agg, Varnish/purge, etc. !

Test your deliveries with all those that have been activated, measure load/server responses starting from Sprint 1, force your teams to develop in a performance-oriented way. !

Idea: Ecommerce is performance-oriented development.

From re-use to platformmakeupforever.com

Countries, Languages, Multi-site system: Re-use of modules !

Import/Export, Workflow: partial re-use !

ERP: connectors to SAP or JDEdwards may be partially exchanged !

Same platform: features may be exchanged

WHY DRUPAL?

Open Source, with the largest community in the world = no lock down !

20,000 existing and modules = maintainable !

Robust and tested: 13 years, White House, The Economist, BBC, Warner… !

Flexible: How to’s, UGC, video sections, personalization, engraving, community, academy, mini-sites…

Number one (or two ;) Drupal Shop in EMEA

Thanks ! You can download slides of this presentation on slideshare !

OR

Throw us rotten tomates !

@Adyax

top related