Let’s take an example of a hardware business ABC having presence all over the North American continent with the United States as its central office. ABC sells its hardware through different brand names. ABC procured AEM license and wants to set up a website leveraging the Multi-Site Manager (MSM) feature.
- ABC multi-brand, multi-regional and multi-lingual presence.
- Content centrally authored in United States (us) / English (en).
- Regional / Language variations constitute 80% of content from us/en.
- Regional sites may have certain hardware product pages that are absent in the US site.
- ABC engages 3rd parties for translation services.
- Changes in language variations within a region managed by the regional team.
BUSINESS REQUIREMENTS
- Ability to “roll out” centrally authored content from US/English to all other regional and language variations.
- The regional authoring team shall have the ability to tweak the content and add additional pages if required.
- Ability to push content selectively from US/English.
- Need governance process in place for publishing changes from regional teams.
- Regional teams shall have the ability to change only their regional sites.
- Ability to re-use content across brands.
- Translation to be done only once per language for every change.
SOLUTION – CONTENT DISTRIBUTION VIEW
Language masters are unpublished pages for all languages accessible only by power author to avoid translating the same content multiple times.
Language masters are set as a blueprint and all other brands and regional sites are the sites created from the blueprint.
US/EN is the source of content with Master/EN as its live copy. A live copy has a synchronized (or modify) event as a trigger and follows the standard live sync rollout config.
Master/EN to other master sites is managed through language copy translation workflow.
Push to brand and regional sites from blueprint managed through the MSM blueprint center with the trigger as “roll out” and follow standard live sync rollout config.
Language masters are unpublished pages for all languages accessible only by power author to avoid translating the same content multiple times.
Language masters are set as a blueprint and all other brands and regional sites are the sites created from the blueprint.
US/EN is the source of content with Master/EN as its live copy. A live copy has a synchronized (or modify) event as a trigger and follows the standard live sync rollout config.
Master/EN to other master sites is managed through language copy translation workflow.
Push to brand and regional sites from blueprint managed through the MSM blueprint center with the trigger as “roll out” and follow standard live sync rollout config.
SITE STRUCTURE
DESIGN SUMMARY
- Ability to “roll out” centrally authored content from US/English to all other regional and language variations. [Solution] Leveraged Multi-Site Management (MSM) feature to distribute content from US/EN for regions.
- The regional authoring team shall have the ability to tweak the content and add additional pages if required. [Solution] Regional sites are made as MSM live copies. They permit canceling the inheritance and changing the content.
- Ability to push content selectively from US/English. [Solution] Leveraged MSM blueprint center to “roll out” content to desired sites.
- Need governance process in place for publishing changes from regional teams. [Solution] Publishing workflow should take care of this.
- Regional teams shall have the ability to change only their regional sites. [Solution] To be managed by ACL.
- Ability to re-use content across brands. [Solution] Site structure allow this.
- Translation to be done only once per language for every change. [Solution] Usage of language masters does this.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.