Blueprint Scenarios. Websites offering Content in different Languages for different countries

Introduction
The purpose of this post is to solve a Blueprint design exercise based on some specific requirements.
The intended audience for this article are individuals that want to gain knowledge of how to analyze and design using SDL Tridion Blueprint Principles.
In this exercise an important concept in design is introduced, which is a country agnostic layer.

Scenario
Websites created for different countries offering content in different languages

Requirements
A company wants to design a blueprint model for produce similar websites for different countries.

Each website will be showing content in the different official languages of the country.
Example: Canada will require two websites, one in English and one in French.


Company is trying to maximize the reuse of translated content and allow content translated to a specific language to be reused by other countries where that language is spoken, however, that content could be localized and the original translation could be adapted or additional content specific to the country could be added.


Current websites required are US (English), Canada (English, French) and France (French)

Pages must be centralized for all countries, but additional pages could be added per country if required.  

The Websites of the same country in different languages must follow the same structure.


Solution
This scenario has requirements related to content and content translation reuse, but still allow flexibility for any country to add specific content and pages.
The following diagram represents the blueprint structure.
Each box represents a Publication and the red arrows show the inheritance between publications 

        0000 Empty Parent Publication is the Scalability Level, is left empty

1000 Schema Master Publication is used for create the Schemas and Categories

2000 Design Master Publication is used for create the design artifacts 

2000 Content Master (LN-EN) Publication is used for create the Content Master (English), which contains the content that is available for all websites. As is common content, must be country agnostic, content is not for an specific country.

3000 Content Master (LN-FR) Publication is used for translate the common content from English to French. This translated content will be used for produce any website where content is delivered in French Language.

3000 Master Structure Publication is used for maintain the global structure of the sites.
 

4001 Content (CO-US-EN)  Publication is used for maintain the content for US in English
Inherits from the publication "2000 Content Master (LN-EN)"

4002 Content (CO-CA-EN) Publication is used for maintain the content for Canada in English
Inherits from the publication "2000 Content Master (LN-EN)"

5001 Content (CO-CA-FR) Publication is used for maintain the content for Canada in French
Is inheriting from the "3000 Content Master (LN-FR) Publication" and also from 
"4001  Content (CO-US-EN) Publication " so any content created for Canada only has to be created
in English and translate to French in this publication 


5001 Content (CO-FR-FR) Publication is used for maintain the content for France in French
Is inheriting also from the "3000 Content Master (LN-FR) Publication", so is reusing the translated content into French Language

The Level 600X represents the websites produced with this blueprint model

6001  www (CO-US-EN)   Publication represents the website for US in English Language
Inherits from the "4001 Content (CO-US-EN) Publication" and "3000 Master Structure Publication"
  
6002  www (CO-CA-EN)   Publication represents the website for Canada in English Language
Inherits from the "4001  Content (CO-CA-EN) Publication" and "3000 Master Structure Publication"

6003  www (CO-CA-FR)   Publication represents the website for Canada in French Language
Inherits from the "5001  Content (CO-CA-FR) Publication" and "3000 Master Structure
Publication"

6004  www (CO-FR-FR)   Publication represents the website for France in French Language
 Inherits from the "5001  Content (CO-CA-FR) Publication" and "3000 Master Structure
Publication"

Appendix:
For the Canadian websites, In case that we require the French language website independent from the
English Language website (not at specified in the requirement), we could handle that following the
next diagram

In this case there is no dependency between the Canadian website in English language and the
Canadian website in French language

Blueprint Scenarios. Website offering Content in different Languages for the same country

Introduction
The purpose of this post is to solve a Blueprint design exercise based on some specific requirements.
The intended audience for this article are individuals that want to gain knowledge of how to analyze and design using SDL Tridion Blueprint Principles

Scenario
Website offering Content in different Languages

Requirements
A company wants to design a blueprint model for produce the website for an specific country in different languages.

Company wants to offer content in 3 different languages, English, Spanish and French
Content must be centralized, created in English and translated into Spanish and French 
Pages must be centralized and have the same structure regardless of the language. The pages created in English language are the pages that drive the structure of the Web Site  

Solution
This is a relatively simple scenario, as there are no requirements of localization except for translation.
The following diagram represents the blueprint structure.
Each box represents a Publication and the red arrows show the inheritance between publications

       0000 Publication is the Scalability Level, is left empty

       1000 Publication is used for create the Schemas and Categories

2000 Publications are used for create the Content Master (English) and Design Master
Using this layer we achieve the centralization of the Content.

2001  Publications are used for Translate the Content into French and Spanish

3001  Publication  is used to maintain the master structure (The structure of the WebSite itself)
Using this layer we achieve the centralization of the Pages.


4001, 4002, 4003  Publications are used to maintain the pages. 
Those publications are not going to be used much, as all the structure, assemble of content in pages happens at the master structure

Note: This solution is just an example. Depending on how we dive into requirements, this solution could have some small variations:

1) We could create another publication inheriting from Content Master also for English Content
2) We could remove the 4001 www (EN) and use the 3001 Master Structure for maintain the English structure