Companies experience their greatest growing pains when expanding business to global markets. It’s an exciting time but can also be a rude awakening as differing local requirements emerge for both product and content.
On the content side, keeping all of these requirements in check can be a daunting task. Proper planning and execution is critical for meeting these requirements and delivery dates, and for keeping your sanity.
This guest post is by Carlos Evia, Ph.D., the director of Professional and Technical Writing at Virginia Tech.
The DITA Troubleshooting topic is one of the “new” features in version 1.3 of the standard. However, troubleshooting has been around the DITA world for some good eight years now.
This post provides an overview of techniques you can use to handle conditional content in DITA. The need for complex conditions is a common reason organizations choose DITA as their content model. As conditional requirements get more complex, the basic Show/Hide functionality offered in many desktop publishing tools is no longer sufficient.
Conditional processing is especially interesting–or maybe problematic—when you combine it with reuse requirements. You identify a piece of content that could be reused except for one small bit that needs to be different in the two reuse scenarios.
Robert Anderson, one of the DITA architects, compared the transition from DITA 1.1 to DITA 1.2 to the difference between having a couple of drinks with friends and a huge party. The DITA 1.2 specification introduced broad changes in the form of new base elements, new architectural structures, and new specializations.
DITA 1.3 isn’t the rowdy gathering that DITA 1.2 was—it’s more a group of friends going out to the new pub downtown while being sure to get some designated drivers. This article describes the most important additions to DITA 1.3.
Yes, you need another “best of 2014” list to round out the year. Without further ado, here are Scriptorium’s top 2014 blog posts on content strategy, DITA, and localization.
Your industrial products become part of well-oiled machines. Unfortunately, your workflow for developing product literature may not be as well-oiled.
What’s the first thing that comes to your mind when I say “XML and content”? If large technical documents and back-end databases pop into your mind, you’re in good company. But many content-heavy groups can benefit from adopting XML. Marketing is one of these groups.
In this webcast, Sarah O’Keefe provides a basic introduction to XML and explains how it could affect your content creation efforts. This presentation emphasizes the overall concept and has minimal technical content.
Everyone wants to know how much an XML workflow is going to cost. For some reason, our prospective clients are rarely satisfied with the standard consultant answer of “It depends.”
This post outlines typical XML projects at four different budget levels: less than $50,000, $150K, $500K, and more than $500K.
The companies described are fictional composites. You should not make any major budgetary (or life) decisions based on these rough estimates. Your mileage may vary. Insert any other disclaimers I have forgotten.
How can you implement DITA content strategy? Is DITA itself a content strategy?
A DITA implementation isn’t merely a matter of picking tools. Several factors, including wrangling the different groups affected by an implementation, are critical to successfully managing DITA projects.
Note: This post assumes you have already done a content strategy analysis, which determined the DITA standard supports your company’s business goals.
Wondering about a transition from desktop publishing to XML publishing for your content? Check out our new business case calculator.
You’ve made the transition to an XML workflow for publishing your technical content, converted all of your legacy content, and started authoring in the new system, as discussed in part 1 of this post. Although you now have a much better outlook on sustainability, you’re still facing a problem: your content creators are having trouble with the idea of separating content from formatting.
Your publishing workflow has been the same for years, but new technology, different customer requirements, and company growth are making you realize you might need a change. Your print-based processes won’t always be sustainable, and XML is looking like a possibility for the future. There’s just one problem: you have thousands of pages of legacy content that you’ll need to convert, and it’s not exactly XML-friendly.
or, What you need to know before you start working on a DITA to InDesign project.
The basic idea of structured content—separate storage of content and formatting—is changing production workflows and, increasingly, content creation tools. In FrameMaker 12, Adobe joins the party on the tech comm side.
“It’s not about the tools.” Except when it’s totally about the tools.
Because the phrase “best practices” is boring, we provide, for your reading pleasure, the ten commandments of DITA.
In this webcast recording, Sarah O’Keefe discusses content strategy and the role of DITA in content strategy.
I’m about to replace an old toilet, not-so-affectionately nicknamed the Lazy River.
So, you’ve decided to move to a DITA-based workflow. Before you convert your existing content to DITA, consider these five tips, which encompass both big-picture and coding-specific issues.
Reuse and automated formatting are the most common justifications for XML, but recently, we have heard a new reason from several customers: rebranding.
In the world of superheroes, technical writers could just slide down a pole or do a clandestine spin to transform themselves into DITA technologists. Of course, nothing is that easy, so what does the transformation from tech writer to DITA superhero really require?
