CoreMedia Content Cloud v11 Upgrade Guide / Version 2110
Table Of ContentsWith CoreMedia Content Cloud v11, a new API for localizing content types has been introduced. The background for this change is that content type localizations need to work in both the Main Studio App and the new Workflow App. The previous way of localizing content types (solely via resource bundle keys) has some drawbacks, so this was the opportunity to rework it. The main drawbacks are:
The localization resource bundle keys were rarely directly used in code. Instead, usages resulted from string concatenation. This untyped access of bundle keys prevents IDE support and makes assessment of refactorings hard.
Customizing icons was only supported in the form of style classes. No direct convenient usage of SVG icons was possible.
The new API addresses both issues but at the cost of one extra bit of configuration. The new API is described in-depth in Section 9.5, “Document Type Model” in Studio Developer Manual.
This upgrade section shows how a typical use case can be migrated. In addition, you will learn the usage of a converter tool that migrates existing content type localizations.
Note that the previous API for localizing content types is still in place as a fallback, but it only works for the Main Studio App. Localizing content types for the Workflow App requires using the new API, so it is recommended to use the new API for both apps to take advantage of shared code (see below).
