SDL Tridion BluePrint – Minimizing Localizations

This article explains the importance of SDL Tridion BluePrint Localization and its consequences. Also, it gives support for your BluePrint design and localization standards by using a rule of thumb Minimizing Localizations

Note: Do not try this at home!!! If you are not familiar with SDL Tridion BluePrint, perhaps you should think about getting support from someone that does.
In the long term, you will find that it was worth every cent.

The setup

SDL Tridion BluePrint Localization allows us to adapt something generic to a more concrete context. In this way, we can create “global” items that are shared across a number of websites. When needed, the item can be localized to adapt it to the context of a particular website without affecting the others.

For example, a product marketing description may be good for most of the websites. We create the product marketing description globally. Then we may adapt the product marketing description to a particular website by localizing it.

 The consequences

The consequence of that localization is that changes in the global item will not be push down to the localized item.

This means that every time you localize an item you lose a bit of SDL Tridion:

·         Reusability: Localized items need to be managed individually.

·         Maintainability: Managing individual copies increases the work load of your editors

·         Cost efficiency: as a conscience of the two items above.

Of course, it is fine to localize when you gain something with it. For example, provide the right content in the context of a market or a website.

Also, remember that you may localize an item to obtain a gain, but this also means that you take ownership of the future upkeep of the localized item.

The possible approaches and solutions

We have found that some common localization points are avoidable by using alternative approaches and solutions. For example, in terms of translation you should seriously consider the following:

·         Use a single Translation Layer in the BluePrint

·         Manage web page title and metadata in components in the global content publication

·         Manage Navigation, breadcrumbs and  sitemap titles as content in the global content publication

Note: we should provably explain in depth these approaches and solutions.

The Conclusion

BluePrint Localization is a very very good thing, although it has consequences.

Minimizing localization will help you construct a more solid and robust SDL Tridion implementation, increasing reusability, maintainability and user friendliness, while reducing costs.

In general, avoiding localizations has more advantages than disadvantages, but you would not be very happy if BluePrint localization was not possible.

What is proposed here is minimizing localizations, when and if possible.

Keeping in mind the advantages and disadvantages of minimizing localizations will help you making the right decisions:

·         Advantages

o   Improve central control over items - Managed once use everywhere

o   Minimize maintenance -Managed once use everywhere

o   User friendly - Minimize editorial tasks and work load

·         Disadvantage

o   Less flexibility