Skip to main content
Level 1
October 26, 2026
Question

Add Custom Dita Attribute to a paragraph tag

I'm trying to add a custom attribute to the standard DITA <p> element in AEM Guides On-Premise.

I created a custom DTD containing a custom attribute definition for <p> and placed it under /apps/fmdita/dita_resources. I also created a custom catalog.xml in the same location and added it to the DITA Profile under Schema → Catalogs.

When I define and use a custom public identifier (for example, -//Test//Test DITA Topic//EN) in the catalog and use the same identifier in the topic DOCTYPE, the custom attribute is recognized and available in the editor.

However, my goal is to extend the standard DITA topic model used by existing content. To achieve this, I tried using the OOTB public identifier -//OASIS//DTD DITA Topic//EN in my custom catalog and DTD configuration. The custom attribute is not recognized when the topic uses the standard DITA DOCTYPE with the OOTB public identifier.

My assumption is that the out-of-the-box DITA catalog/DTD is taking precedence over my custom catalog entry.

Has anyone successfully extended the standard DITA Topic DTD in AEM Guides?

Specifically, I'm trying to understand:

  • Is it possible to override or extend the OOTB -//OASIS//DTD DITA Topic//EN mapping through a custom catalog?
  • Does AEM Guides always prioritize the OOTB DITA catalogs over custom catalogs added through the DITA Profile?
  • What is the recommended approach for adding a custom attribute to existing DITA elements such as <p> without changing the DOCTYPE of existing topics?
  • Has anyone implemented a similar requirement

Any guidance, best practices, or working examples would be greatly appreciated.

Thanks


 https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/install-conf-guide/global-folder-profiles/conf-profiles#id1889D0I305Z

https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/install-conf-guide/custom-dita-ot-cs/dita-ot-specialization#id211MB0E00XA