Publish Translated Content

Learn how to publish your translated content and update the translations as the content updates.

The Story So Far

In the previous document of the AEM headless translation journey, Translate Content, you learned how to use AEM Translation Projects to translate your headless content. You should now:

• Understand what a translation project is.
• Be able to create translation projects.
• Use translation projects to translate your headless content.

Now that your initial translation is complete, this article takes you through the next step of publishing that content and what to do to update your translations as the underlying content in the language root changes.

Objective

This document helps you understand how to publish headless content in AEM and how to create a continual workflow to keep your translations up-to-date. After reading this document, you should:

• Understand the author-publish model of AEM.
• Know how to publish your translated content.
• Be able to implement a continual update model for your translated content.

AEM’s Author-Publish Model

Before you publish your content, it is a good idea to understand AEM’s author-publish model. In simplified terms, AEM divides users of the system into two groups.

1. Those who create and manage the content and the system
2. Those who consume the content from the system

AEM is therefore physically separated into two instances.

1. The author instance is the system where content authors and administrators work to create and manage content.
2. The publish instance is the system that delivers the content to the consumers.

Once content is created on the author instance, it must be transferred to the publish instance for it to be available for consumption. The process of transferring from author to publish is called publication.

Publishing Your Translated Content

Once you are happy with the state of your translated content, it must be published so headless services can consume it. This task is not the responsibility of the translation specialist, but is documented here to illustrate the complete workflow.

The simplest way to publish the translations is to navigate to the project assets folder.

/content/dam/<your-project>/

Under this path you have sub-folders for each translation language and can choose which to publish.

1. Go to Navigation -> Assets -> Files and open the project folder.
2. Here you see the language root folder and all other language folders. Select the localized language or languages that you wish to publish.
   
3. Tap or click Manage Publication.
4. In the Manage Publication window, make sure that Publish is automatically selected under Action and that Now is selected under Scheduling. Tap or click Next.
   
5. In the next Manage Publication window, confirm that the proper path(s) is/are selected. Tap or click Publish.
   
6. AEM confirms the publish action with a pop-up message at the top of the screen.
   

Your translated headless content is now published! It can now be accessed and consumed by your headless services.

There are additional options when publishing your content, such as scheduling a publication time, which are beyond the scope of this journey. See the Additional Resources section at the end of the document for more information.

Updating Your Translated Content

Translation is rarely a one-off exercise. Typically your content authors continue to add to and modify your content in the language root after initial translation is complete. This means that you must also update your translated content.

Specific project requirements define how often you must update your translations and what decision process is followed before performing an update. Once you have decided to update your translations, the process in AEM is simple. As the initial translation was based on a translation project, so too are any updates.

However as before, the process differs slightly if you chose to automatically create your translation project or manually create your translation project.

Updating an Automatically Created Translation Project

1. Navigate to Navigation -> Assets -> Files. Remember that headless content in AEM is stored as assets known as Content Fragments.
2. Select the language root of your project. In this case, /content/dam/wknd/en is selected.
3. Tap or click the rail selector and show the References panel.
4. Tap or click Language Copies.
5. Check the Language Copies checkbox.
6. Expand the section Update Language Copies at the bottom of the references panel.
7. In the Project dropdown, select Add to an existing Translation Project.
8. In the Existing Translation Project dropdown, select the project created for the initial translation.
9. Tap or click Start.

The content is added to the existing translation project. To view the translation project:

1. Navigate to Navigation -> Projects.
2. Tap or click the project that you just updated.
3. Tap or click the language or one of the languages that you updated.

You see that new job cards are added to the project as appropriate.

You may notice that the statistics listed on the new card (number of assets and content fragments) is different. This is because AEM recognizes what has changed since the last translation and only includes the content that must be translated. This includes re-translation of updated content and the first-time translation of new content.

From this point, you start and manage your translation job just as you did the original.

Updating a Manually Created Translation Project

To update a translation, you can add a new job to your existing project that is responsible for translating the updated content.

1. Navigate to Navigation -> Projects.

2. Tap or click the project that you must update.

3. Tap or click the Add button at the top of the window.

4. In the Add Tile window, tap or click Translation Job and then Submit.

   

5. On the card of the new translation job, tap or click the chevron button at the top of the card, and select Update Target to define the target language of the new job.

   

6. In the Select Target Language dialog, use the drop-down to select the language and tap or click Done.

   

7. Once your new translation job’s target language is set, tap or click the ellipsis button at the bottom of the job card to view the details of the job.

8. The job is empty when first created. Add content to the job by tapping or clicking the Add button and using the path browser as you did before when originally creating the translation project.

From this point, you start and manage your translation job just as you did the original.

End of the Journey?

Congratulations! You have completed the headless translation journey! You should now:

• Have an overview of what headless content delivery is.
• Have a basic Understanding AEM’s headless features.
• Understand AEM’s translation features and how they related to headless content.
• Have the ability to start translating your own headless content.

You are now ready to translate your own headless content in AEM. However AEM is a powerful tool and there are many additional options available. Check out some of the additional resources available in the Additional Resources section to learn more about the features you saw in this journey.

Additional Resources

• Managing Translation Projects - Learn the details of translation projects and additional features such as human translation workflows and multi-language projects.
• Authoring concepts - Learn about the author and publish model of AEM in more detail. This document is focused on authoring pages rather than Content Fragments, but the theory still applies.
• Publishing Pages - Learn about the additional features available when publishing content. This document is focused on authoring pages rather than Content Fragments, but the theory still applies.
• Authoring Environment and Tools - AEM provides various mechanisms for organizing and editing your content including a robust path browser.

Business.Adobe.com resources