Translation BluePrint best practices
This section provides recommendations on the design of your BluePrint for Translation Manager.
In your Translation BluePrint you need to take account of the following:
- Do not mix languages in a single Source Publication—a Publication is assigned a single translation language when you configure a Publication for Translation.
- Create a language layer in your BluePrint with Publications configured as Target Publications that contain only translated content. This best practices ensure that you do the following:
- Have a clean distinction between translated content and local content added by content authors
- Can re-purpose content to other channels, for example an email campaign
- Under the Target Publications in your language layer, create the following:
- Child Publications
- Local Folders and Structure Groups in which content authors can add local content
- By default, the translation management system is the owner of the translated content. If you update a translated item (local copy) in Content Manager Explorer and then send the item out again for translation, the translation management system will overwrite the changes because the Translation Memory has no knowledge of the update. There are two methods you can use to guard against this problem.
- If content authors are permitted to add local content in a Target Publication, you can implement a naming convention where local Folders and Structure Groups where authors can add local content are clearly marked. You can assign users and groups specific permissions to define user access to Folders, Structure Groups, and Categories to ensure that content authors do not update translated content.
- Enable the Review feature. This method enables Tridion Sites authors to review the translation segments (drafts) before the translation is complete, and to modify them as needed. This way, the desired modifications are saved to Translation Memory in the translation system.