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.
Content strategy is taking hold across numerous organizations. Bad content is riskier and riskier because of the transparency and accountability in today’s social media–driven world.
But now, we have a new problem: a talent deficit in content strategy.
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.
It’s a new year, which means it’s time for Scriptorium to discuss—and wildly speculate about—the latest trends in content. Here’s what Bill Swallow, Gretyl Kinsey, and I had to say about 2015 content trends.
We hear a lot about the learning curve for structured authoring, but what does that really mean?
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.
Or: A stranger takes over the Scriptorium blog and gets all enthusiastic about tone of voice
Merry Christmas, Scriptorium readers. And, Sarah O’Keefe, an especially Merry Christmas to you. I’m your writer, Santa, and this is your Blog Secret Santa gift. (Everyone else: yep, hi. I’m a random stranger writing for Sarah’s blog. Because Christmas is fun.)
And here’s your present: Four websites that perform the rare magic trick of taking things that are normally really boring and making them entertaining.
Localization—the process of adapting content to a specific locale—is a critical requirement for global companies. It’s often treated as a necessary evil, but this is shortsighted. The quality of localization efforts affects the company’s bottom line.
More than ever, products and services are sought, purchased, and consumed in multiple language markets. Proper localization practices are critical to drive sales, and they can save you time and money in production.
This article describes best practices for efficient, effective localization.
