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.
When I first started writing in DITA, two things helped me become productive quickly. One was my knowledge of other mark-up languages and the other was not a skill but more a mindset or approach to documentation. Even when I used FrameMaker, I always thought of the documentation as a collection of topics rather than a linear chain of information like a book. I took a few workshops and training sessions on minimalism, structured writing, and modular writing, which strengthened my skills in writing in that form.
Over the years I have introduced a lot of writers to DITA and that mindset-topic-based writing versus linear writing-is the main stumbling block for a lot of writers. Those who are used to linear writing often have greater difficulty adapting to the principles on which DITA was founded.
Now, writing in DITA is one thing . . . working with the DITA toolkit is a whole other matter. THAT requires some skill. :)
On Monday, August 20, 2012, Kari Gulbrandsen wrote:
> Oops. I hit send too soon. I had the same questions about DITA.
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.