Take the DITA challenge

More and more companies are realizing that it’s time for a paradigm shift in the way they manage and distribute their technical content. The DITA* methodology combines topic-centric authoring with an XML-based, end-to-end architecture for authoring, producing, and delivering technical information.

*Darwin Information Typing Architecture

Could your organization improve its documentation processes and save money with a structured writing solution?

Answer these questions to find out:

• Is your content being re-used?
• Does the same content appear in multiple documents and help files but you don't have a methodology for ensuring consistency?
• Do chunks of content get re-used from version to version while only parts of a document change?
• Does the same content get published in multiple formats like PDF and on-line help?
• Do chunks of content appear in different documents on related topics? For example, in a system overview spec, an installation guide and an operator’s guide?
• Are your documents translated into other languages?

Contact JBS for a consultation on structured documentation

Monster Documents

Most companies have got at least a few of these. It might be a combo doc: User Guide, Installation and Reference manual and some APIs thrown in for good measure. It's probably been around for a few years and gets updated so frequently that it's a patch on a patch on a patch. The document's users have got some kind of crazy methodology for finding the information they need, but others just give up. You know that this monster needs fixing but you can't figure out how.

Contact JBS for a consultation on how to tame your monster documents!