When content strategy fails, RoadRunner edition
Our home Internet connection is usually reliable, but today I come home to what I think must be an outage. No Internet on any of our Wifi networks.
Our home Internet connection is usually reliable, but today I come home to what I think must be an outage. No Internet on any of our Wifi networks.
One of the axioms of technical communication is to keep things simple. But sometimes, complex communication is the better alternative.
Some patterns are beginning to emerge as we apply content strategy to technical information.
Some thoughts on technical communication, content strategy, and the state of the industry at tekom/tcworld 2012.
In this webcast recording, guests Alyssa Fox (NetIQ) and Toni Mantych (ADP) discuss their differing DITA implementation decisions.
In which we develop narrative content in a modular architecture.
This webcast recording is a preview of our new Content Strategy 101 book, which will be released in September. Here, Sarah O’Keefe discusses why content strategy is important and how you can use it to transform your technical content from “necessary evil” to a business asset.
When selecting authoring and publishing tools, there is an unfortunate human instinct to cling to the familiar. This ranges from a slight preference for the tool currently in use to “You will pry this software from my cold, dead hands.”
In this webcast recording, Sarah O’Keefe gives an overview of DITA, one of the major structured authoring standards in tech comm. You’ll also learn about DITA concepts, the business case for DITA, and typical scenarios where DITA is used.
The problem: DITA does not provide a default mechanism for encoding context-sensitive help information. This article discusses a new approach that avoids specialization and provides a maintainable approach for context-sensitive help mapping.