Skip to main content

Content management

Business case/ROI Content management Content reuse DITA DITA XML—authors Localization Structured content Translation

Reduce translation costs with XML

$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.

Read More
Content management DITA Taxonomy

SubjectScheme explained

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.

Read More
Content management DITA Localization

The second wave of DITA

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.

Read More
Content lifecycle Content management Food & fun

Plumber’s guide to content workflows

Last week I was working in my home office when I heard an odd hissing sound. Upon investigation, I found that my hot water heater had decided to empty itself onto the basement floor.

Fortunately I had some failsafes in place; the heater’s pressure release valve was doing its job by routing scalding hot water onto the floor, and my floor is slightly slanted toward a drain in the floor. This got me thinking (because my brain is oddly wired this way) about failsafes in content workflows.

Read More
Content management

Reducing tedium in content workflows with exceptionally mobile technology

The content lifecycle can involve many needlessly tedious tasks. Perhaps the most tedious of tasks is review tracking. There are many ways to send content out for review. Some people prefer using a manual process, others prefer automated workflows. Whatever approach you use is fine, provided one critical detail: that the reviewer actually read the material.

To date there is no sure-fire way to ensure that reviewers read the material assigned to them. No matter how many alerts they receive, and no matter how many times you bug them, there is no systematic way to ensure that reviewers read and comment on the material in a timely manner.

But what if there was?

Read More
Content management Replatforming Structured content

Content strategy: What’s your exit strategy?

You’ve probably heard the announcement countless times: “Please locate the nearest emergency exit.” Chances are you ignore these exits most of the time, but you feel safer knowing they’re there. You wouldn’t go to a restaurant or movie theater or travel on public transportation that didn’t have an emergency exit—so why would you develop a content strategy without one?

In a recent blog post, Alan Pringle brought up the the importance of having an exit strategy, and I wanted to expand on that idea. Without a plan for what to do if your implementation doesn’t go as expected, your company could face tremendous costs—in terms of both time and money—trying to move on to a system that works.

Read More
Business case/ROI CCMS Content management

Buyer’s guide to CCMS evaluation and selection

“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.

Read More