TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Yves gives excellent advice. One step not to skip is to generally audit your current content. Look for compatibilities/incompatibilities... Look for how the content should map to DITA. You can find lots of information out there to help direct this level of the effort.
I have to second Yves' suggestion for pre-defining your procedures, concepts, reference topics if you plan to use those divisions. Typically, you will go from a given heading level to any one of those... That means you have a 1-to-many translation. In effect, you're adding information into your source. There's no way to increase the resolution without manually doing the work. So you should go ahead and start on that. It will teach you a lot about your content, and ties in nicely with an audit anyway.
cud
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
