Start here for a guided journey through translating your headless content using AEM's powerful translation tools.
Headless implementation is increasingly becoming important for delivering experiences to your audience, wherever they are and regardless of channel, region, or locale.
Headless implementation forgoes page and component management as is traditional in full stack solutions and focuses on the creation of channel-neutral, reusable fragments of content and their cross-channel delivery. By using AEM's powerful translation tools, these reusable fragments can be easily translated and delivered to your audience wherever it may be.
This guide leads you through the most important headless translation topics so that on completion you:
The goal is to give you a broad understanding of headless technology, how AEM serves headless content, and how you can translate it. If you are not familiar with any of these topics, this is your ideal place to start.
If you are already familiar with AEM, headless, and translation, you may already have the foundational knowledge of this journey. 🔗
Documentation Journeys are designed around best practices principles, informed by Adobe's latest research, proven implementation experience from Adobe consultants, and feedback from customer projects.
This journey is designed for the translation specialist persona, often referred to as the Translation Project Manager or TPM. This journey lays out the requirements, steps, and approach to translate headless content in AEM. The journey may define additional personas with which the translation specialist must interact, but the point-of-view for the journey is that of the translation specialist.
This journey assumes the reader has experience translating content on a large CMS system, but assumes no knowledge of headless technology or AEM.
The following are the personas that interact in this journey.
|Grupo de usuarios||Descripción||Role in Journey|
|Translation Specialist||Defines what content should be translated and manages those workflows||Audience of this journey|
|Content Author||Creates and manage content that is delivered headlessly||Content Authors create content that the translation specialist must translate.|
|Administrador||Manages the base setup and configuration of AEM||The translation specialist works with the administrator to make configuration changes needed for translation such as installing a translation connector.|
|Content Architect||Analyzes the requirements for the data that must be delivered headlessly and defines the structure for this data||Translation specialists work with the content architect to define the organization of the content so it can be easily translated.|
Information in this journey can of course be useful to all personas, but some information may be superfluous to certain roles. 🔗
You will explore many topics in this journey. The following articles give you foundational knowledge of translating headless content in AEM and link out to detailed technical documentation.
Although you can go directly to a particular part of the journey, many concepts build on ones in previous articles. Therefore if you are new to headless translation in AEM, we recommend that you start at the beginning and progress sequentially.
|0||AEM Headless Translation Journey||Este documento|
|1||🔗||Learn headless concepts, how they map to AEM, and the theory of AEM translation.|
|2||🔗||Get to know how to organize your headless content and how AEM's translation tools work.|
|3||🔗||Learn how to connect AEM to a translation service.|
|4||🔗||Learn how to define translation rules to identify content for translation.|
|5||🔗||Use the translation connector and rules to translate your headless content.|
|6||🔗||Learn how to publish your translated content and update the translation when the underlying content is updated.|
You are now ready to get started on your Adobe headless translation journey. 🔗
Documentation journeys show you how AEM solves a business problem by providing a narrative that guides you through complex, interrelated processes and features. A journey illustrates how multiple features work together to serve a single business need.
As such journeys are designed to stand on their own. However a number of them can be related to each other. Check out these additional journeys for more information on how AEM's powerful features work together.