The tcworld China event took place in Shanghai April 18 and 19. I was there to present on content strategy and advanced DITA (yes, I hear your gasp of surprise), but for me, the most interesting part of the trip was getting a chance to connect with the technical communication community in China.
It is a common stereotype that an XML workflow for content is rigid, unbending, and free of creativity.
Let’s wrap up 2015 with a look back at popular posts from the year.
Scriptorium wishes you the best for 2016!
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
We’re about to begin the last quarter of 2015, and that means CONFERENCES. Scriptorium is attending many tech comm and content strategy events.
Will we see you at these conferences?
The roles and responsibilities in an XML (and/or DITA) environment are a little different than in a traditional page layout environment. Figuring out where to move people is a key part of your implementation strategy.
“What CCMS should we buy?”
It’s a common question with no easy answer. This article provides a roadmap for CCMS evaluation and selection.
First, a few definitions. A CCMS (component content management system) is different from a CMS (content management system). You need a CCMS to manage chunks of information, such as reusable warnings, topics, or other small bits of information that are then assembled into larger documents. A CMS is for managing the results, like white papers, user manuals, and other documents.
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.
Your industrial products become part of well-oiled machines. Unfortunately, your workflow for developing product literature may not be as well-oiled.
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.
