Jim Owens's blog
Some visitors to xml.dita.org may be wondering what all the fuss is about. Presumably, they are looking for answers to their technical publication problems (unless they have come here accidentally while enquiring into Ms. von Teese's burlesque entertainments). Is DITA right for them?
One of the tools we're using is the FM_DITA Application Pack beta recently released by Adobe. With this, you can develop DITA topics, map them into documents, and then generate a book from the map.
We need time and resources to identify new technologies and methods, evaluate them, and adopt the ones that show promise. At the same time, we need to continue developing and delivering information to customers using our traditional tools. Is there a way forward that offers minimal disruption to our current processes?
This is the story of a typical software documentation shop. We use unstructured Frame and WebWorks. We deliver PDF and CHM. We deliver in several languages. We deliver customized documents for different markets. We barely have enough time and people as it is -- and there are new products, languages, and markets on the way.