Thread

Hi everyone,

Has anybody truly globalized with EE?  I know there’s multi-language modules, but that’s not quite enough.  My goals:

-Single global CMS platform
-Master template modifiable for various global markets (e.g. images, language, widgets, etc…)
-When master template changes, locals are notified to update their version
-Single content repository with master content and localized content
-When master content changes, locals are notified to update their version

I think I could do this, but I’m looking to start a discussion with someone that already has.

-Tim

Hi Tim,

I’m afraid you’ll have to find someone who can code a set of extensions/modules for you, as your list of requirements are quite specific.

A little birdie told me that Leevi Graham is working on a Multi Language module and his add-ons are always top notch, but I doubt even that one will fit your needs completely. Mind you… that Multi Language module is not done yet.

Greetz,
Wouter

Hey, thanks for the reply.  I’m interested in the way CMSs will evolve to meet this issue.  There’s long been the idea that translating content allows you to deploy a site globally.  Simply put: not true.  There’s an enormous amount of localization required that goes beyond language that must occur at the template level.  Consider different product offering, target market, skin color, navigation preferences, AC voltage (charging circuitry troubleshooting), forums, pricing, SEO, adverting partners… the list is extensive.  As a result, the bigger companies staff web departments that each run sites on separate technology in various world-wide regions.  Very little is shared. 

For us smaller companies, we don’t have the resources to deploy this stuff globally, even though we do business abroad.  Just coordinating information is difficult. 

Anyway - here’s to hoping!!!

-Tim

Hi, Tim,

If you were to make use of the Multiple Site Manager, you can share content and templates across Sites using Site Variables and Parameters.  In this way you wouldn’t even need to notify “localized” content to update their sites - it would simply be rolled out as it’d be handled in one location.

The tricky part is if you need that minor separation wherein you do give them a chance to stage content over.  You could possibly do this with content by using a custom field for each piece of content, and something like Solspace.com’s Entry Notifier to notify those that need to know that the content has changed.  Templates may be a bit more difficult.

I think that you can achieve most of your goal with EE + MSM combo, you may just need to divert a bit from your idealized workflow.