Having problems with inconsistently written documentation? Do your user manuals need some help themselves? If so, then you need a style guide for your technical writing team. We’re not talking about what they should wear, but how they should write.
Content couturier Keith Schengili-Roberts (IXIASOFT) talks about what they are, why you need them and how to use them effectively. While not exclusively focusing on DITA, Keith will also talk about why a style guide is a necessity for any team working with DITA.
Continue reading “Style Guides: Fashionable But Also Practical [On-Line Event]”
In this TC Dojo session, we’ll talk about maps, maps, and more maps. Using maps to organize your thoughts, your keys, your content, your deliverables. We’ll talk about mini-maps and deliverable maps, and why you should not use bookmaps (unless you actually print to paper, but who does that anymore?!).
Continue reading “Get your [bleep] together…with DITA maps [On-Line Event]”
If your documentation process is implicated in a customer quality incident (CQI), Congratulations! You have the platform needed to shine a light on the problems you’ve been escalating for years.
In this presentation, Seth Park will argue that errors in documentation are actually symptoms of underlying data flow issues. If you don’t get involved in root-cause analysis, you’ll end up being asked for more reviews and checklists when you really need a more effective method for transferring data amongst teams. Continue reading “How to use root-cause analysis to promote information supply chain methodologies [On-line Event]”