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.
Will cheap content cost your organization more in the long run? In this webinar, host Sarah O’Keefe and guest Dawn Stevens share how poor workflows, inaccurate source data, and the commoditization race can undermine both product quality and brand trust. Sarah and Dawn also discuss why strategic staffing and mature content ops create the foundation your AI initiatives need to deliver reliable content at scale.
Sarah O’Keefe: I write content that’s great for today. Tomorrow, a new development occurs, and my content is now wrong. We’re down the road of “entropy always wins.” We’re heading towards chaos, and if we don’t care for the content, it’ll fall apart. So what does it look like to have a well-functioning organization with an appropriate balance of automation, AI, and staffing?
Dawn Stevens: I think that goes back to the age-old question of, “What are the skills that we really think are valuable?” We have to see technical documentation as part of the product, not just supporting the product. That means that we, as writers, are involved in all of the design. As we design the documentation, we’re helping design the UX.
What happens when AI accelerates faster than your content can keep up? In this podcast, host Sarah O’Keefe and guest Michael Iantosca break down the current state of AI in content operations and what it means for documentation teams and executives. Together, they offer a forward-thinking look at how professionals can respond, adapt, and lead in a rapidly shifting landscape.
Sarah O’Keefe: How do you talk to executives about this? How do you find that balance between the promise of what these new tool sets can do for us, what automation looks like, and the risk that is introduced by the limitations of the technology? What’s the roadmap for somebody that’s trying to navigate this with people that are all-in on just getting the AI to do it?
Michael Iantosca: We need to remind them that the current state of AI still carries with it a probabilistic nature. And no matter what we do, unless we add more deterministic structural methods to guardrail it, things are going to be wrong even when all the input is right.