I came across a question today on LinkedIn asking “What’s stopping the wider use of DITA within your company?”.

Some of the responses that were given included reasons like

• I don’t have time right now to do this
• I did this at my last job, and it cost me my job
• Too hard to migrate content to DITA
• Too expensive to buy the tools

What really surprised me was that I don’t think most people really understood the question. I believe the question was asking, what is stopping other departments using DITA, not what is stopping more technical writers on more projects using DITA.

In my experience, which is very broad, the key factor that is “stopping the wider use of DITA within organizations” is that DITA is a content model designed to meet the needs of producing technical product documentation, more specifically software documentation and is not applicable, or even easily adapted outside that use case. DITA was after all designed by IBM to meet their internal requirements and has not changed much since entering the public domain.

The other major factor is that outside professional writers, like technical communicators, users lack the skills, discipline, and desire to be able to understand or use the complex set of technologies and tools required to make DITA work. It’s simply too hard.

To make matters worse, even professional writers struggle with DITA and many organizations are abandoning their DITA (and other XML) implementations in favor of less complex and more user-friendly solutions that can be easily adopted across the organization by users of all skill levels.

Last year we replaced dozens of DITA and XML based implementations with Author-it, in large and small companies alike. I remember meeting with one particular group that had been working with DITA for about a year and was very adamant that it was the only way to do it. During the presentation of Author it we showed them how easily they could migrate their DITA content, do everything they were doing with their XML based tool set, and much more, while continuing to use the DITA content model and validation within Author-it. Needless to say they are now happy Author-it users.

Paul Trotter
Founder and CEO
Author-it Software Corporation

The year 2006 was an exciting year, for all sorts of reasons. It was an exciting year for Author-it Software Corporation when Author-it 4.3 was released with support for the still-embryonic DITA standard. Who knew, in 2006, that DITA would come so far? (Well, we did, obviously.) As Author-it is a controlled authoring tool, built on top of a component content management system, with a multi-channel publishing engine back end, we were pretty much the first end-to-end DITA solution. (After all, end-to-end is such a fluid description. Just because we have more at the starting end (authoring), the finishing end (publishing), and that lumpy bit in the middle (content management), what’s to stop someone else from picking up the pegs and moving them closer together to create their own definition… sigh).

The independent CMS Watch published an industry report in 2008 covering DITA tools, XML, and component content management systems. As one of the few vendors providing a end-to-end DITA solution Author-it rated very highly. High praise indeed. Author-it being an out of the box solution that requires no third party tools or programming certainly helped. Interested in the report? If you are reading this you should be*. 2009 version out soon, I believe.

I don’t want to sound fussy, but first usually means… first. And 2006 is definitely before 2009. So unless I’m missing a very finely tuned definition of ‘First Authoring Software to Support DITA Publishing With No Programming or Third-Party Tools Required’ that somehow magically makes 2009 occur before 2006, I think someone at MadCap is taking liberties with the truth. Now I like Lewis Carroll and George Orwell as much as the next person but such blatant and farcical manipulation of the truth should remain in works of fiction. Or people should hire PR companies that do their homework.

Or, we could agree that MadCap has never let the truth get in the way of a good story. Lovely folks at MadCap, and Flare works very well and lots of people like it, but if no one else is going to call them on the blatantly inaccurate press releases seen over the past year, I will.

Posted by Matthew Armstrong, Sales Director Asia Pacific, Author-it Software Corporation

*From the CMS Watch website:
About the Report
The XML & Component Content Management Report 2009 provides an overview of leading CCM products as well as XML editing tools, including detailed comparative evaluations of 25 CCM vendors XML editing products.
How it will help you
The report can help your team:

• Save time in the selection process
• Create an effective vendor shortlist
• Avoid selecting the wrong product
• Budget more accurately
• Avoid painful setbacks

Who needs this report?
Check out this report if you are considering to undertake any of the following projects:

• Complex content re-use
• Extensive content translation
• Technical Documentation and other DITA projects
• Structuring common office documents
• Multichannel publishing
• Structured authoring with XML editors
• Managing information components at an enterprise level