Four years later, PDF is not dead
This post is part of Scriptorium’s 20th anniversary celebration.
In 2013, I wrote that PDF is not dead. Four years later, it’s still too early to write the obituary.
This post is part of Scriptorium’s 20th anniversary celebration.
In 2013, I wrote that PDF is not dead. Four years later, it’s still too early to write the obituary.
This post is part of Scriptorium’s 20th anniversary celebration.
In addition to Scriptorium’s twentieth anniversary, 2017 marks the twelfth year for this blog, which started in April 2005 with a grudging And another one bites the dust… post.
A content strategy implementation requires you to address multiple technical facets: tool and process integration, specifications for how content is delivered, and so on. These technical details, however, are of little interest to the executives who control funding. They are much more interested in seeing results to justify continued spending.
We’ve written before on what lurks beneath the surface of an InDesign file, and how drastically it differs from the DITA standard. When you’re looking at going from DITA to InDesign, though, there’s a lot that you need to take into consideration before you jump in.
Web sites are fantastic at content delivery and generally terrible for content authoring. If you’re old enough (like me), you may have experienced the pain of hand-coding HTML or even editing HTML files live on your web server.
$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.
What factors affect content strategy decisions? Every client has a different combination of requirements, and of course there are always outliers. But based on our consulting experience, here are some factors that affect content strategy decisions.
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.
A few months ago, I wrote about how you could benefit from having a test bed for your content. I made mention of use cases several times, but what are they, and how can you make them effective?
When I first started as a QA tech at a small game company, I was immediately thrown into the QA test bed. It was a place where we could test production-ready content without being interrupted by ongoing development or server restarts. Functionality was well-documented and could be used to test against our users’ bug reports.
Translating content for foreign markets can be an expensive and time-consuming endeavor. While it’s important to keep costs in check, the critical element to watch is quality. The only sure-fire way to ensure quality in translation is to build it into your source.
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.
Content creation should no longer be the exclusive domain of full-time writers. Employees in other departments can offer valuable information that your company’s content should capture. Where can you find these part-time contributors?
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
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.
“My team is looking into how we can use <incumbent tool> to handle our new content requirements.”
That’s what I heard from a manager during a recent phone call about a company’s expanding content needs. The tools-focused response made me cringe.
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?
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.
“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.
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.
The novels of Italian author Elena Ferrante are getting a lot of attention, but “Elena Ferrante” doesn’t actually exist. The writer behind the pen name prefers anonymity and shies away from publicity. Creators of corporate content should take a few pointers from the author when seeking recognition for their work.
When remodeling your kitchen, would you replace 1980s almond melamine cabinets with the same thing? Probably not. (I certainly wouldn’t!) Then why make the content strategy mistake of using new tools to re-create the old formatting in your content?
For his 1959 horror movie The Tingler, director/producer William Castle had movie theater seats rigged with buzzers to scare moviegoers during a scene when the Tingler creature is loose in a theater. Patrons in those seats probably didn’t enjoy the jolt—or making a spectacle of themselves because of the Tingler’s “attack.”
Quick! What’s the first thing you think about when you want to change your content strategy (the way you produce and distribute content)? If your answer is “tools,” you’re in good company.