I'm interested in Drupal, DITA and elearning. And in building a Drupal Learning Content Component Management System (LCCMS). Structured authoring is a great fit for elearning as well as tech comm. There is also a DITA standard for elearning. Much of the functionality for Drupal DITA tech comm CMS would be directly applicable to elearning, like single source authoring, content re-use, multi-channel publishing.

One key difference is that elearning relies much more heavily on interactivity and rich media elements.

I've successfully imported the "Growing Flowers" example from the DITA sample files that come with oXygen using the DITA XHTML to Simple HTML XSLT template. The DITA XML files have been transformed to XHTML for importing.

A week ago I wrote a post here about how we could build a DITA CCMS in Drupal, I've now written a full blogpost about it, with a screencast that explains how it could work. You can check it on our blog, it's titled A free and open source DITA CCMS

At Drupalcamp Cluj in Romania I got really excited again about the possibility for building a CCMS (component content management system) in Drupal.

Ages ago when we did our first experiments with DITA in Drupal this was our goal. We did a prototype for a tool that was able to do single pass transformations of topics, allowed you to manage DITA maps in a mindmap and that had a form for creating DITA topics.

I’d like to share a recent project with you that I think may provide a solution to problems you’re facing in publishing tech comm content using Drupal. This is my first post on Drupal.org after registering two days ago, so bear with me as I tell you the [somewhat long] story of how I used Drupal to solve the problem of publishing technical documentation online.

Working as a Technical Writer in a software company, I am responsible for publishing documentation on Drupal. There is a need to shift from PDF publishing to online publishing on Drupal.

After doing careful research on Drupal.org, I found the Import HTML module. Since we author on FrameMaker DITA authoring tool, a list of DITA files are created. To be able to import, we convert the DITA files to XHTML using DITA-OT. This process is straightforward.

When you create a Wiki page, Discussion, etc. in this group, please put DITA in the title. Thanks!

Reasons:
- SEO (search engine optimization) so people will get these pages if they search for DITA Drupal or something like that on Drupal.org or Google or whatever.
- Understanding what is in search results - most search results pages show titles and maybe a short excerpt, so having a meaningful title like "Useful modules for DITA" as opposed to just "Useful modules" is important.

"The Drupal implementation for dita.xml.org has been a long-standing source of pain, and we want to redo the site in early 2015," they write. Shouldn't that be a challenge for the Drupal community and/or some of the larger Drupal companies to prove them wrong?

Not being a DITA expert, I'm not sure if the AsciiDoc tool chain can be used for DITA per se, but it is useful for technical documentation in general. So it may be of interest to some people in this group that I have created a "sandbox" module on Drupal.org that does some AsciiDoc integration with Drupal.