Create and store structured content in Drupal

Typical Needs:

  1. Structured content authoring tool
  2. Generation of DITA XML artifacts
  3. Saving of XML artifacts to Drupal as chunks: topics in nodes, maps in menus, taxonomies or books
  4. The editor may be external or internal.
  5. The editor may serve the professional developer of structured content or the occasional user.
  6. Import/Conversion of Word documents

Likely Implementation on Drupal:

  1. EXTERNAL EDITOR. Saves XML files in GIT repository. Import from GIT using Migrate module or Version Control API module
  2. INTERNAL EDITOR SAVING AS BLOB. Saves XML files as a single blob in node (topics and maps). This will require a post-save process or cron job to save the content as chunks in multiple nodes.
  3. INTERNAL EDITOR SAVING AS CHUNKS. Saves XML files as chunks in multiple nodes (topics) and in menus, taxonomies or books (maps).

Jeff Eaton talk at DrupalCon Austin

The Battle For The Body Field: Drupal And The Future Of Wysiwyg. Jeff doesn’t address how to implement DITA, but rather shows how DITA can show how Drupal can be improved. Conveys that there is a market need for DITA capable editors in the Drupal CMS.

  1. 03:00 We need chunks instead of blobs
  2. 05:50 Need to store meaning (in chunks), and then transform it for display
  3. 10:00 Drupal does chunks (teasers, blocks)
  4. 13:15 But the body field is still a miniblob (not a chunk)
  5. 26:30 WYSIWYG makes the problem worse
  6. 28:40 How DITA stores meaning
  7. 35:30 How DITA is extensible
  8. 36:50 How DITA uses placeholders
  9. 39:00 How DITA tailors the editing tool to the domain, not the output

Possible 3rd Party Integrations: