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.
Visiting Dojo Expert
Keith Schengili-Roberts is a DITA Information Architect at IXIASOFT, DITA evangelist and technical writing nerd. Keith is also an award-winning lecturer on Information Architecture at the University of Toronto’s iSchool, and Durham College. He is also an active member of the OASIS DITA Technical Committee, and can often be found presenting at conferences, working with customers, and researching how DITA is being used and sharing those results with the DITA community.
Keith’s popular industry blog DITAWriter.com has become a focal point on DITA resources and best practices. Connect with Keith on Twitter @KeithIXIASOFT.
Watch the Video
Recorded: April 2017
View the Slides
You might also be interested in...
Using Style Guides to Achieve Content Collaboration and Consistency
Liz Fraley, Single-Sourcing Solutions
Building a style guide from the ground up
Cathy Jones, Jack Henry & Assoc.
DITA output can be pretty
Liz Fraley, Single-Sourcing Solutions
Styling DITA in Arbortext is easy
Liz Fraley, Single-Sourcing Solutions
Key Concepts:
Filed under:
About the TC Dojo
At the TC Dojo, you pick the topics and we find the experts. Join our mailing list so you can attend the next one live. After all, you can't ask questions of a video.