Perils of DITA publishing, part 1: Writing
In which we develop narrative content in a modular architecture.
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.
The mantra of XML is that you separate content from formatting. Authors do content; formatting happens later. During a panel discussion at last week’s (excellent) UA Europe conference, I realized that this is only half the story.
The batch publishing paradigm is deeply ingrained in technical communication, and breaking out of it is going to make the transition from desktop publishing to structured authoring look easy.
We all know that Lorem Ipsum is not your friend. But sometimes, even sample content fails.
In this interactive session, technical communication experts Sarah O’Keefe, Nicky Bleiel, and Tony Self give their opinions about important current topics in the industry.