Alexander Dade

All samples

Localizing content in Heretto

Procedure for technical users in a component content management system

Context

This project trained teams to translate content into other languages. I worked with developers and IAM engineers to define the practices and protocols. It was part of an enterprise content migration to XML that reduced maintenance costs and increased daily users.

The guide walks technical users through preparing content for translation, creating a localization job, and exchanging translation packages, with practices for working with translation teams. A second stage used retrospectives to audit the training program.

Tools: DITA, XML, XLIFF, Heretto CCMS, Okta SSO

What to notice

  • Bold headings make the page easy to navigate.
  • Numbered steps carry the sequence. Bullets carry the detail inside each step.
  • Steps are in the second person and start with a verb.
  • Interface objects are bold so the reader can spot the action they need to take.
  • Each screenshot sits directly under the step it shows.

The document

Creating a localization job

You can manage and translate your content for different languages and regions with localization jobs.

Start by creating maps to handle translations. A map is your starting point for any translation project. It groups the content to be translated. From these maps, you can create localization jobs. In the Jobs tab, you create translation packages.

Download the translation package and send it to your translation team.

  1. Prepare the content for translation.
    • Organize all the content to be translated into a map.

      Note: This map is the container for the topics you need to translate.

    • Verify that the map includes all needed topics and that the content is ready for translation.
    File list showing a map and three topics, each with Approved status.
  2. Create a localization job.
    • Click the Map and select Jobs.
    Map details panel with the Jobs icon circled in the left sidebar.
    • Click the Create Localization Job button and select the Source Package or XLIFF job type.
    Create Localization Job button.
    • Select the target language. Optionally, set a due date and include any notes relevant to the translation job.
    • Click the Create button.
    Create Localization Job dialog with job type Source Package, content Map.ditamap, and locale de-de German.
  3. Download and send the localization package.
    • Click the job and click Download Localization Package.
    Job details with the Download Localization Package link circled.
    • Review the package contents to confirm it includes the correct files for translation. There should be two files: the new language and the source language reference.
    Folder listing with project-notes.txt, a de-de folder, and a source-language-reference folder.
    • Send the zip package to your translation team. Instruct the team to translate the content without changing the file structure or names. Only change the text inside the elements, not the XML structure.
  4. Receive and upload the translated content.
    • After the translation is complete, receive the translated package from your team.
    • Upload the package back into Heretto.
    Upload localization package dialog with a file drop area.
    • Confirm that the two language codes match. Select Include and click Apply.
    Upload dialog matching de-de from the upload to de-de in Heretto, with Include checked.
    • Heretto automatically associates the translated content with the source files.
  5. Review and publish the translated content.
    • Review the uploaded translations to confirm accuracy and completeness.
    • Click the Complete Job button.
    Complete Job button.