The best of 2016
As the new year begins, the Scriptorium team is looking back at our blog posts for 2016.
We wish you the best in 2017—and watch for merriment during the year as we celebrate our 20th anniversary.
Content strategy for technical communication
Content strategy is planning to use information to advance an organization’s goals. Your organization should have an enterprise content strategy that covers all customer-facing information, both persuasive content and informational content.
For technical content, an enterprise content strategy means identifying business goals and then setting up a content development and delivery system that supports those goals.
Going for the gold with your content strategy
Your content strategy should outline the goals you plan to accomplish. Once you’ve implemented that strategy, you can see how well your new content development processes line up with those goals. Gretyl Kinsey explains how you can figure out whether your content strategy was a success.
Top eight signs it’s time to move to XML
How do you know it’s time to move to XML? Consult our handy list of indicators.
One of the most common questions we hear is, “How do we make our localization process better?”
When we’re asked this question, we turn the question around. What is wrong with your current localization process? What would you like to improve? How do you define “better?”
Read Bill Swallow’s series of posts on getting the best value for your localization efforts.
LearningDITA and Oxygen XML Web Author
Using Oxygen XML Web Author, anyone can take free DITA training without downloading and installing an XML editor on their computer.
Case study: InDesign XML for well-designed print layouts
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?
If you want more information about getting DITA content into InDesign, here are the gruesome details.
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.
What was your favorite Scriptorium post of the year? Leave it in the comments.