Documentation Center

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).
By default, Keywords used in Components are sent for translation but are stripped when returned to the Content Manager.
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
If you must translate Structure Groups and Folders, you can define security in a Structure Group or Folder at a higher level and localize Structure Groups and Folders at a lower level and have these inherit security setting from the parent, for example the Building Blocks Folder. Alternatively, you can unlocalize the Content Manager item to get the updates and send the content for translation again.
Translate Structure Groups if you need to translate the URL structure of a site, for example if your implementation in some way makes use of the URL.
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.
Translate Pages if you do not want regional Web sites affected when a Parent changes.
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:
  1. Create a Metadata Schema.
  2. Add fields to the Schema and set the field type to Component Link.
  3. Create a dummy Component.
  4. Add the link to a field and send the Component for translation.
A Structure Group or Folder that uses the Metadata Schema gets the translated content automatically. A downside to this approach is that every field in the Metadata Schema must be a Component Link, and for every different value for the field you need to create a meta Component.