Revisiting the ROI of DITA
This post is part of Scriptorium’s 20th anniversary celebration.
Back in 2011, I wrote a post on how to calculate the ROI of DITA.
This post is part of Scriptorium’s 20th anniversary celebration.
Back in 2011, I wrote a post on how to calculate the ROI of DITA.
00:02 Gretyl Kinsey: Welcome to the Content Strategy Experts podcast brought to you by Scriptorium. Since 1997 Scriptorium has helped companies manage, structure, organize, and distribute content in an efficient way. In Episode 16, we discuss DITA specialization.
Scriptorium is hosting a live, interactive question and answer session about the authoring courses on LearningDITA.com! Whether you want to go over a specific exercise or you just need some help getting started, bring your questions and join us for the discussion.
00:03 Gretyl Kinsey: Welcome to The Content Strategy Experts podcast brought to you by Scriptorium. Since 1997, Scriptorium has helped companies manage, structure, organize, and distribute content in an efficient way. In episode 14, we discuss the DITA Learning and Training specialization.
Here in the United States, the summer is now officially over and students are back to school. For many, this means a change in routine and a fresh outlook on the remainder of the year. This is an excellent time to direct that fresh outlook to your content by measuring your content strategy ROI.
I’ve written in the past on how a QA mindset can improve the quality and consistency of your content. While having a robust test set and test plan are useful, there’s another tool that you can use.
Coauthored by Sarah O’Keefe and Alan Pringle
First published in 2001.
Structured authoring and XML represent a significant paradigm shift in content creation. Implementing structured authoring with XML allows organizations to enforce content organization requirements. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the effort required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations.
Getting your DITA content into a high-design format like InDesign is a tricky prospect. The biggest stumbling block is the fact that there is no intrinsic link between your ICML and the template that you flow it into. In the end, your InDesign template (you’re using one, right?) is the most important part of a DITA to ICML workflow; it contains the actual styles that will control how your output appears.
We’ve written before on what lurks beneath the surface of an InDesign file, and how drastically it differs from the DITA standard. When you’re looking at going from DITA to InDesign, though, there’s a lot that you need to take into consideration before you jump in.
Web sites are fantastic at content delivery and generally terrible for content authoring. If you’re old enough (like me), you may have experienced the pain of hand-coding HTML or even editing HTML files live on your web server.
Thinking about migrating unstructured content to XML? Take a hard look at your existing desktop publishing workflow. The maturity of your DTP process will have a big impact on a move to XML.
Following a template-based DTP workflow is not just about implementing best-practice processes. Templates make a potential move to XML less expensive and painful.
$0.21 per word.
That’s the average cost in the US to translate content into another language according to Slator, a translation news and analytics site. That number is not speculative; they analyzed the costs per word from over 80 actual proposals gathered by the US General Services Administration (GSA). You can view the source proposals here.
For LavaCon Dublin, Sarah O’Keefe and I delivered a case study presentation on some of the roadblocks we have encountered in implementing DITA at ADP. This article summarizes the key points of the presentation. The presentation and this blog do not represent the views of ADP, LLC.
Your project is coming along nicely. You have your workflow ready, your style guides are composed, and things are looking up. However, you have complex metadata needs that are starting to cause problems. You need a way to ensure that authors are only using valid attribute values, and that your publication pipeline isn’t going to suffer. This is a situation that calls for a subjectScheme.
More than 900 people have signed up for our free DITA courses on LearningDITA.com—thank you! You’ve had a basic introduction to DITA and learned how to write concept, task, reference, and glossary topics. Now you can learn how to collect those topics and establish relationships among them with our newest course: Using maps and bookmaps.
Automated PDF formatting works well for technical communication. But what about highly designed content for printed books? How can companies enable flexibility in print/PDF layouts generated from structured content?
You have DITA. Now what?
More companies are asking this question as DITA adoption increases. For many of our customers, the first wave of DITA means deciding whether it’s a good fit for their content. The companies that choose to implement DITA find that it increases the overall efficiency of content production with better reuse, automated formatting, and so on.
In this webcast recording, Scriptorium’s Alan Pringle, Bill Swallow, and Gretyl Kinsey look at 2016 trends in content and content strategy. Sarah O’Keefe moderates.
It is a common stereotype that an XML workflow for content is rigid, unbending, and free of creativity.
One of the greatest benefits of using DITA is specialization. However, specialized DITA is more challenging and expensive to implement than standard, out-of-the-box DITA, which is something you should consider before you take the plunge.
How do you know it’s time to move to XML? Consult our handy list of indicators.
Let’s wrap up 2015 with a look back at popular posts from the year.
Scriptorium wishes you the best for 2016!
When you’re coming up with a metadata strategy for your content, you should start by developing a taxonomy, or a hierarchy used to organize metadata. A taxonomy will help shape your metadata strategy and make implementation of that strategy possible. In this follow-up post to Making metadata in DITA work for you, you’ll learn some tips for creating a taxonomy that will succeed in helping your audience—both internal and external—find what they need.
In a recent post on lean content strategy, I wrote about a focus on waste reduction:
After creating a nice automated XML-based process, waste in formatting is eliminated, and we declare victory and go home. Unfortunately, the organization is now producing irrelevant content faster, and the content organization is now positioned as only a cost center.
Is your content perceived as a commodity?