Adobe Experience Manager Guides

In AEM Guides Editor Console, there is a button to save the dita/ditamap as a new Version.  I have a requirement to create version of dita document programmatically based on updated event.How can I achieve this programmatically?

In our DITA content, sometimes we have a <fig> with no <title> inside, and sometimes there's a title.We move the title to the bottom, and so in the cases where a title is present in the <fig>, we want to give the <fig> element some padding at the bottom... but only in the cases where the <fig> has a <title>. In the intermediate HTML, the <fig> becomes <figure>, and the <title> becomes <figcaption>. So, in our CSS for making a Native PDF, I set up a very simple pseudo-class:figure:has(figcaption) {border: 0.5pt solid blue;padding-bottom: 24pt;} ...with the border there so I could see whether the element was being selected. When I output the merged HTML and look at it in Chrome or Edge, this works fine. In the output PDF, however, this doesn't work. The element is not selected and is not formatted.So, I'm wondering if there are any special considerations for using pseudo-classes in CSS with Native PDF... or a

Is it possible to configure the Native PDF to create fillable fields, or do you have to use DITA-OT with a 3rd party plug-in or Acrobat tools on a generated PDF to create a PDF form? 

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 an example. You have some AEM metadata, say "docstate" or "publisher" or "description" in AEM metadata schema, and you want to show this metadata on front page of the PDF output. Where we are:1. Managing the publication/ditamap metadata in AEM assets2. And the publication is published to PDF output using DITA-OT (pdf2 plugin)                   IMPLEMENTATION Part 1: Setup metadata in AEM Add custom metadata fields in AEM as desired (for this example 'docstate', 'description' were available out of the box, we added the 'publisher' field in this case using AEM Metadata Schema) Add a metadata field 'published' as shown in screenshot

I have several concepts and tasks that won't change from draft state to anything else. Overall, these files are maybe only 5% of the files so far that do move from draft to in-review to approved document states. I cannot see any commonalities. The topics that have moved states just fine are in a variety of versions (1.0, 1,1, 1.2), have or don't have variables and conditions. The topics that won't move states are valid DITA and do not have any DITA specializations. Has anyone seen this before? AEM Guides (UUID) v4.2 On-Prem InstallationAEM 6.5.15 On-Prem Installation

Is there a way to bulk change objects/assets' Document States? Doing it one topic at a time is okay if your map only has a handful of topics, but this isn't going to be feasible for large maps. AEM Guides (UUID) v4.2 On-Prem Installation (late April/early May 2023)AEM 6.5.15 On-Prem Installation

Nested Chapters or topic tiles take different heading levels and different styling. Is there any configuration to apply common styling to all chapters/topics titles particularly?

hi,       With respect to AEM GUIDES, SMART Tagging feature is not available OOB. Pl refer below screenshot both yellow highlighted and red encircled. Help needed to apply SMART Tags…to the DITA Topics.                Also it would be great, if the differences of functionality that is available and not available in the AEM Guides Cloud SDK? Regards,SK

I have created ui_config.json file in the /apps/fmdita/xmleditor/ui_config.json and made few customizations for the Guides xmleditor header bar. Still the header is rendering ui_config.json code from the libs folder(/libs/fmdita/clientlibs/clientlibs/xmleditor/ui_config.json)Can someone please suggest how to make /apps/fmdita/xmleditor/ui_config.json  work for Guides xmleditor headers.

Hi,I am generating DITA-OT pdf output preset in QA environment and its failing with the below File not found exception even though the file exists in the folder. The same DITA-OT.zip is working in stage environment. /mnt/crx/author/crx-quickstart/profiles/ditaot--5557edd8-83f8-b342-5539-9d1cebc9be88/DITA-OT/plugins/org.dita.pdf2/build.xml:276: javax.xml.transform.TransformerConfigurationException: Failed to compile stylesheet. 5 errors detected. at net.sf.saxon.PreparedStylesheet.prepare(PreparedStylesheet.java:176) at net.sf.saxon.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:139) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.readTemplates(TraXLiaison.java:308) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.createTransformer(TraXLiaison.java:322) at org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:188) at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:881) at org.apache.tools.ant.taskdefs.XSLTProces

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. version 3.8 of AEM Guides includes DITA-OT version 3.3.2) There are scenarios in which you may want to customize the DITA-OT supplied with product, those scenarios can be: Using/Adding a custom plugin (to generate a style/branded output or a custom built plugin to get output in desired format, or integrating existing plugins) Using a different version of DITA-OT (may be using the latest version, or using a legacy version on which your plugins were built)   Things to Remember when adding such customization There are few things to keep in mind to make sure the integration of customized DITA-OT works successfully in AEM Guides. These pointers are scenario dependent, which are listed

I'd like to be able to indicate changed text within my topics by a different color for reviewers. Can text be changed/highlighted in a different color, either in source or author view, as an alternative to using tracked changes?Thanks!

Is it possible to use a custom panel as a browser to provide help for the writers when using the editor? If I author the custom help in DITA in AEM and generate in any one of the formats available, can I add a (?) icon to the left navigation that opens the panel with a search bar and the TOC for 'how do I' help for authors? Is there any guidance for this type of customization aside from how to add the icon?Having to send writers to the AEM site to see the generic help to use the editor, and then to another location to see the customized authoring guide is not ideal. Having the help topics integrated into the editor would be better. How do other companies handle the integration of their custom authoring help wikis or sites into the tool?  What I'm thinking is a solution like this one - https://experienceleaguecommunities.adobe.com/t5/experience-manager-guides/publishing-customizing-the-ditamap-dashboard-quot-output-tab/td-p/563729 that allows you to preview sites con

@aswinilakshminarayanan 

Hi, I have a need with the new database feature in Guides 4.3 to use some math functions in the Velocity Template. Essentially I would like to use this: Velocity - MathTool (apache.org) in my Velocity template.I know that I need to include this reference in the context of Velocity, and I have access to our sites codebase. Where can I put the MathTool reference so I can use it in my .vm file?  

AEM Guides v4.2 On-Prem Installation In the Templates > Page Layout screen, the option to turn on the Glossary output is grayed out and cannot be selected. I can turn on and off the List of Figures, List of Tables, and Index, but not the Glossary. How do I turn on the Glossary option to generate a glossary when using a BookMap?

Hello -- I am unable to see the list of topics contained in a map in the Manage > Baseline view in the web editor. Also, double-clicking on a baseline doesn't allow me to see the list of all topics contained in a map; it just opens the edit baseline dialogue box. Any help on how to fix this would be appreciated.

Hi all, I am trying to include custom javascript in the aem guides (DITA topic) but my changes are not getting reflected. Also Is there anyway we can debug javascript written by us that we have included to generate PDF. This is related to Native PDF publishing

Has anyone gotten the use-by-reference footnotes to work in Native PDF Publishing? The output works as expected in the default DITA-OT output, but it isn't working as expected in Native PDF Publishing. What am I missing?

Hi Team, I am generating JSON output presets for the ditamaps and its failing. Below error showing in the history.log file.[DOTA001F][FATAL] "dita" is not a recognized transformation type. Supported transformation types are bcmhtml5, bcmpdf, bcpdf, ca)bcpdf, ca_bcpdf, eclipsehelp, html5, htmlhelp, javahelp, msd_bcpdf, pdf, pdf2, sym_bcpdf, tocjs, troff, xhtml. Please ssuggest.Thanks 

Hi, We are trying to use the Post generation workflow to run our own custom workflow.Our last step is AEM Guides Finalize Post Generation:The output on AEM Guides is getting well generated and green: However we are getting always an item on our AEM inbox -> Output notification -> Output Generation complete. This is generated immediately after the dita file is converted to our output type (before our custom workflow completes).  How can we remote that output notification, or only send it after our workflow fully completes. Thanks

We publish our content in PDFs. Currently, annotating a PDF file in AEM is pretty cumbersome and highly un-user-friendly. I was wondering if there is any way to integrate Adobe Acrobat with AEM so we can leverage the editing tools available in there.

The default EPUB output doesn't seem to work at all. Has anyone had any luck? It doesn't seem to understand SVGs, but even after removing all SVGs from the map, just to test it, the default output fails and says the ditamap is "outside the scope of the input/dita map directory." Does anyone know what's going on? There are no DITA specializations in this simple testing map. And I'm not seeing anything in the AEM Guides v4.2 Installation and Configuration Guide.

Hello,I want to set the DITA Open Toolkit parameter "validate" to "false" during PDF generation. How can I accomplish this in the PDF output preset?I have tried setting DITA-OT Command Line Arguments to --validate=false but get an error because the output preset generates the output via Ant instead of the command line.Best regards,Frank    

Hello, We want to add Asset metadata that is attached to DITA files to the JSON output. We already pass the required metadata as properties to the DITA-OT. I suppose, including this metadata in the JSON output requires a DITA-OT plugin? If so, how would I implement this? Best regards,Frank