Umbraco's translation features are not unlike those in many other CMSs' implementations. Umbraco employs an industry standard workflow that allows translation agencies to be part of the mix without having full access to the content or permission to publish anything to the public site. Umbraco generates a translation file in XML format that the translator user logs in to pick up. The translator user edits the file or uses an industry standard translation program to parse the XML file, makes the necessary translations, saves the file, and finally uploads the translated content back to Umbraco.
Chapter 2 covers in detail how to set up a user with restricted access, delves into granular permissions, and discusses setting multiple start nodes for content access.
To start a Workflow, you need to register a user (as was covered in Chapter 2, in the section “Umbraco Building Blocks”), give him access to the Translation section, and tell Umbraco where he should start in the content tree (in this case the start node is Runway Website (se). The complete user details should look like those shown in Figure 7-11.
A translation user has access to a restricted version of the Umbraco backoffice. In the example in the “Working with Hostnames” section, you set the start node for the translation user, but in a translation workflow that is a fruitless exercise because the user ...