Experience Manager Guides

Join us for an exclusive event for content professionals in banking, financial services, and insurance. Gain insights on digital transformation, artificial intelligence (AI), and structured content management.Adobe CONTENT STRATEGY LEADERS LIVEFree & Virtual | Aug 27, 8:45 AM – 12:15 PM PDTHere’s wh...

REQUIREMENT You are managing DITA content in AEM, and you want to publish that content to (say) PDF output. But you have metadata for your publication(ditamap) managed as AEM metadata - and you want to pass this metadata to the publishing engine to use it in the output.   Let us understand this with...

The toolbar in web-editor is completely customizable, there are many customizations that you can achieve, few use cases would be : Add/Remove toolbar options. Examples : Add a button to make the text bold or remove the insert multimedia option from the toolbar as it is not used frequently.Add a cust...

Problem Statement You are using XML Documentation to author XML/DITA content and one of the publish output is AEM Sites.You want to use an existing AEM Sites template in order to use the pre-designed header/footer (branding, styles etc.) used on your marketing or end user portal (instead of out-of-t...

Problem Statement: Are you facing issue on author instance where preview of DITA asset is not rendering correctly and this happens on asset details page ? Do you see the html encoding rather than actual page UI - Refer the the screenshot below.     Precondition: Do you have dispatcher set up on you...

AEM creates additional version of a media assets when you revert between different versions of the asset. This is functionality as design, as the system: expects that the image version that is currently active may have some work in progress changes and may require saving those before moving to anoth...

Easiest way is to make use of translation=no attribute. Authors can insert the additional attribute as 'translation=no' on the paragraphs that they do not want to translate. The translation vendor needs to be informed and they can do configuration at their end to ignore the text with this attribute....

Background You are using AEM Guides and you publish the DITA content using DITA-OT.   Requirement When using DITA-OT, sometimes you need to use your own version of DITA-OT. The product supplies a specific version of DITA-OT in its release (the latest one when the product version gets released, e.g. ...

The steps to add a custom DITA-OT are documented in the section "Use custom DITA-OT plug-ins" of Installation and Configuration Guide   On a high level the steps are: Get the basic DITA-OT If you want to obtain copy of out-of-the-box DITA-OT from XML Documentation, download it from path "/etc/fmdita...

Step 1: Create a global map for storing your keys. Create a map and add the keyref element to it.     <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "technicalContent/dtd/map.dtd"> <map id="map.ditamap_ffbdbf06-8658-4311-ad84-1c631bba904f"> <title>global-k...

We are pleased to announce that the 3.8 Release for the XML Documentation Solution has been marked GA.   The 3.8 release has been certified on: AEM 6.5 SP8 and SP7AEM 6.4 SP8 and SP7AEM 6.3 SP3   The build has been uploaded on the software distribution portal and can be downloaded from one of the be...