XML overview for executives
How can you implement DITA content strategy? Is DITA itself a content strategy?
In the legal world, discovery refers to the compulsory disclosure of relevant documents. In the consulting world, disclosure also important, but it is usually spotty and not in writing. Instead of disclosure, we have discovery.
We are moving companies away from a heroic model to a process-driven model. Processes are much less exciting that the adrenaline rush that comes from working miracles to deliver the impossible.
Deciding on a content model is a critical step in many of our projects. Should it be DITA or something else? The answer, it seems, often has more to do with our client’s corporate culture than with actual technical requirements.
The Darwin Information Typing Architecture (DITA) provides an XML architecture for technical communication. Although implementing DITA is likely to be faster and easier than building your own XML architecture from the ground up, DITA is not suitable for everyone.
An updated version of this white paper is in Content Strategy 101. Read the entire book free online, or download the free EPUB edition.
Moving a desktop publishing–based workgroup into structured authoring requires authors to master new concepts, such as hierarchical content organization, information chunking with elements, and metadata labeling with attributes. In addition to these technical challenges, the implementation itself presents significant difficulties. This paper describes Scriptorium Publishing’s methodology for implementing structured authoring environments. This document is intended primarily as a roadmap for our clients, but it could be used as a starting point for any implementation.
Mark Wallis of IBM ISS on how to run a successful DITA pilot. Some great information in this presentation on how to reduce risks.
For nine years, the Scriptorium site LearningDITA.com served more than 16,000 students seeking knowledge about the Darwin Information Typing Architecture (DITA) XML standard. A critical system failure forced Scriptorium to rebuild the site, so we focused our consulting expertise on ourselves to address a replatforming challenge for structured learning content.
Your organization’s content debt costs more than you think. In this podcast, host Sarah O’Keefe and guest Dipo Ajose-Coker unpack the five stages of content debt from denial to action. Sarah and Dipo share how to navigate each stage to position your content—and your AI—for accuracy, scalability, and global growth.
The blame stage: “It’s the tools. It’s the process. It’s the people.” Technical writers hear, “We’re going to put you into this department, and we’ll get this person to manage you with this new agile process,” or, “We’ll make you do things this way.” The finger-pointing begins. Tech teams blame the authors. Authors blame the CMS. Leadership questions the ROI of the entire content operations team. This is often where organizations say, “We’ve got to start making a change.” They’re either going to double down and continue building content debt, or they start looking for a scalable solution.
— Dipo Ajose-Coker