DITA at Adobe – The Good, The Bad, The Ugly

If you’re looking for information about real-world use of the Darwin Information Typing Architecture (DITA), check out this interview with Puny Sen, Project Lead, Instructional Communications, Adobe Systems. Sen is candid, sharing the good, the bad and the ugly about the software giant’s foray into the world of the DITA including:

• the percentage of content Adobe was able to reuse
• the difficulties writers faced moving from unstructured to structured FrameMaker
• the need for DITA specialization wizards
• the absence of mature Map editors
• why DITA needs to be constrained
• why information architecture needs to be adapted to DITA
• the flattening of conditional text, attributes, and cross-references
• and the need for a close examination of content granularity prior to adopting DITA

Read the interview

Similar Posts:

• Case Study: Adobe Uses DITA
• Blog Watch: Adobe FrameMaker and DITA
• Sarah O’Keefe on DITA and Adobe FrameMaker