Blueprint Scenarios. Websites offering products in different continents VII

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.
This post continues the previous articles article1, article2, article3, article4, article5, article6 analyzing additional requirements, so is recommended to have a look at those first.

Scenario
Websites offering different products per continent

Requirements
A company that manufactures products in different continents wants to design a blueprint model for maintain all the websites.

In the current analysis session, the following requirements are captured.

In this phase of the requirements is identified how we are going to build the translated websites.

We identify two different scenarios that must be handled differently from Blueprint structure point of view.

Scenario 1: Some Countries will offer the site in a translated language showing the exact same structure than the website produced in the main language. We identified Canada and France following this pattern.

Scenario 2: Some Countries will offer the site in a translated language showing a different structure than the country website produced in the main language. We identified Namibia following this pattern.
Example: Some countries will offer just few pages country specific in the translated language that do not follow necessary the structure of the country main language website  




Solution 
The following diagram represents the changes required in the blueprint.

Scenario 1. Canada and France website in French will inherit from the main websites produced  in English language. Those websites will be pretty much a replica of the main English website, but the content will be translated into French Language.

"9003 www Canada (FR)" is used for create the website of Canada in French Language.
Inherits from publications "8003 www Canada" and "6004 Canada Content (FR)" 

"9005 www France (FR)" is used for create the website of France in French Language.
Inherits from publications "8005 www France" and "6000 France Content (FR)"



Scenario 2. Namibia website in French won't be inheriting from the main website produced for Namibia in English language. That will offer few page with information in French but still will inherit the main structure from the global master and continent master

 

"8000 www Namibia (FR)" is used for create the website of Namibia in French Language.
Inherits from publications "6001 Namibia Content (FR)" and "7000 Master Structure Africa"

Blueprint Scenarios. Websites offering products in different continents VI

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.
This post continues the previous articles article1, article2, article3, article4, article5 analyzing additional requirements, so is recommended to have a look at those first.

Scenario
Websites offering different products per continent

Requirements
A company that manufactures products in different continents wants to design a blueprint model for maintain all the websites.

In the current analysis session, the following requirements are captured.

In this phase of the requirements is identified that translation is required.

Translation must be driven by language, not by country and must reuse as much as possible the translated items.

As languages can have different variations based on the country (Example: French in France can be slightly different than the French in Canada), during the requirements phase we are asked to take that into consideration.

For now we will analyze the Items required to allow translation into French Language for the countries France and Canada, but the design would be the same to cover other Languages. 

Solution 
The following diagram represents the changes required in the blueprint.

The following diagram shows the inheritance in more detail. I removed other inheritance keeping only the inheritance related to translation

"4000 Content Master (FR)" is used for translate the global content into French Language.
Inherits from publication "3000 Content Master"



"5001 Africa Content (FR)" is used for translate the African content into French Language.
Inherits from publication "4001 Africa Content" and "4000 Content Master (FR)"

"5002 America Content (FR)" is used for translate the American content into French Language.
Inherits from publication "4002 America Content" and "4000 Content Master (FR)"

"5003 Europe Content (FR)" is used for translate the European content into French Language.
Inherits from publication "4003 Europe Content" and "4000 Content Master (FR)"

"6004 Canada Content (FR)" is used for translate content created in English in the publication "5000 Canada Content" and the handle any variation of content created in the publications "4000 Content Master (FR)" and  "5002 American Content (FR)" in French specific for Canada (If required) 
Inherits from publication "5002 American Content (FR)" and "5000 Canada Content"

"6000 France Content (FR)" is used for translate content created in English in the publication "5000 France Content" and the handle any variation of content created in the publications "4000 Content Master (FR)" and  "5003 Europe Content (FR)" in French specific for France (If required) 
Inherits from publication "5003 Europe Content (FR)" and "5000 France Content"

Note: Depending on the language standards chosen, maybe is not required to adapt any content inherited from the Global and Continent publications, but if required those are the publications where you will handle that.  

Note: Any countries with similar requirements of translation into French will be handled following the same pattern than the one used for Canada and France.

Note: Any other languages required with follow the same pattern for translation than the French Language.

Learn More
Click here to go to the next section of the exercise 

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