Recommendations for sending content
You must carefully consider what content to send for translation in order to maximize reuse through BluePrinting. This topic provides some guidelines and recommendations for translating content.
- Packaging
- For efficiency, package as many Content Manager items as possible in a single Translation Job. For speed, package relatively few items in a Translation Job and set the priority to high.
- Keywords and Components
- Translate Keywords and Components as much far as possible—these items are the main Content Manager items that contain content and translating these minimizes unnecessary localization. You can send individual Keywords for translation, or the entire Category (the Category itself is not translatable).
- Structure Groups and Folders
-
Avoid translating Structure Groups and Folders as far as possible because:
- changes to your security model (User and Group rights and privileges) are not passed on to Child Publications
- the scope of changes in content is much greater reducing reuse possibilities
- Pages
- Avoid translating Pages if they contain application logic as changes to the logic are not passed on to Child Publications. For example, if you add an image such as a logo.
- Metadata
-
To translate Structure Group or Folder metadata but maintain the link to your security model (User and Group rights and privileges), you can do the following:
- Create a Metadata Schema.
- Add fields to the Schema and set the field type to Component Link.
- Create a dummy Component.
- Add the link to a field and send the Component for translation.