For the past several years, I’ve been hearing about Darwin Information Typing Architecture (DITA) and how it can revolutionize the technical writing process. And for years, I’ve been ignoring the DITA buzz — I was happy with the way I was doing things, single sourcing from Adobe FrameMaker to RoboHelp with some success. But then as I (and my team) started producing more and more documents (while the number of technical writers on our team remained the same), I started thinking that there must be a more efficient way to produce our documents.
So I started looking into what we can change to make our technical writing process more efficient. One answer kept solution — DITA XML. I dug deeper and it appears that it might solve most of the issues and redundancies in our technical writing process.
We recently received the green light from our upper management to dedicate part of our time to figuring out how to get started and implement DITA. And so our DITA XML journey begins and I will be using this website to document our adventures with DITA. Stay tuned.