We would like to have a single location (AEM) for our content. We want to author in DITA and then export/convert the DITA to markdown for use in our GitHub documentation. Also, we would like to import some of our markdown docs into AEM and convert them to DITA so that we no longer need to manage the content in two source systems and use two different markup languages.
XML documentation uses DITA-OT internally to generate the different output. DITA-OT allows the markdown files generation from source dita content and it also lets the author use the raw markdown files for publishing. Please refer below for more details:
More details can be referred here - https://www.dita-ot.org/dev/topics/dita2markdown.html
All the above markdown files types are supported by DITA-OT and can be generated from the XML Documentation Solution by using the relevant transtype. Example – To generate GitHub-Flavored Markdown files, use the markdown_github transtype on the output-preset.
Then you can generate any supported output format e.g. PDF or dita (for normalized dita)
If you need more details OR wanted to discuss your specific use case then please reach out to TechCommSales@adobe.com for a quick demo.
Thanks & Regards,
Thanks Kiran. The problem is when I upload an MD file to AEM, it is not recognized. AEM does not seem to understand what type of file it is.
That is okay. But you should still be able to add that to your map.( Additional information - The authoring of the markdown file in the AEM system is in our roadmap)
If you drag/drop the markdown file into map from xml editor then it will automatically add format attribute also. Do let me know if you want a short demonstration of this.
Thanks & Regards,
Hi! Has the work to enable authoring of markdown in AEM been completed? And if so, do you have any resources or docs to share about it? Thanks!