When you write technical documentation, you manage a great deal of knowledge. Technical communicators evaluate and apply domain knowledge every day. For that, skills in knowledge modeling are extremely useful.
By Alan Pringle (Scriptorium) and Tina Meißner (parson)
This case study shows how Scriptorium Publishing created the free DITA learning website LearningDITA.com by combining the DITA learning and training specialization, GitHub, XSLT, video, and WordPress—and how parson AG adapted those technologies to develop the German site, LearningDITA.de.
Or: What we can do to standardize the content delivery of intelligent information
At this year’s TC world conference, the tekom working group „Information 4.0” introduced the first results of the group’s work for defining a new content delivery standard for technical documentation in the age of Industry 4.0: iiRDS. tekom is the German association for technical communication.
by Katrin Mehl and Elisabeth Fischer
We often present technical information as text. The more complex the information, the more words we have to use. When we describe a complex engine with dozens of components, plugs, and valves, we sometimes need an additional form of presentation, such as an image. Images, like diagrams and illustrations, give the reader a visual layout of components, devices, or technical parts.
In software development, the keyword agile is at least as popular as DITA in technical writing. This is no surprise. Both agile and DITA focus on modularization and the requirements of the users. In this article, we discuss how agile documentation works in practice, recommend tools that support the agile processes and point out the challenges for technical writers.