The PDF roadblock
Getting attractive PDF output out of XML is a serious technical challenge. But in some organizations, the PDF requirement is being used to prevent to unwanted workflow changes.
Author: Sarah O'Keefe
Pitting tech comm and tech support against each other
Technical communication and technical support should be allies. After all, tech support needs the information that tech comm produces. Tech comm often has only limited customer contact; tech support has oodles of daily customer contact.
And yet, there is a common organizational pattern where tech comm and tech support are in conflict.
It’s not easy being…clean
This article was originally published in STC Intercom in March of 2011.
A standards-based workflow is challenging. This article discusses the issues with DITA (an XML standard for technical communication content) and XSL-FO (Extensible Stylesheet Language Formatting Objects, a standard used to create PDF from XML (http://www.w3.org/standards/xml/publishing).
The battle to separate the personal and the professional
Social media is inexorably coalescing our personal and professional identities. What happens when baby pictures, political views, drinking habits, and hobbies collide with your corporate persona?
Webcast: Attractive DITA: it is possible!
In this webcast, Sarah O’Keefe discusses the challenges of getting attractive output from DITA and demonstrates Scriptorium’s approach to web-based help and PDF.
The technical communicator’s survival guide for 2011
At the 2011 North Carolina Technology Association annual meeting, Gartner analyst Michael Smith discussed how IT needs to show business value or risk being marginalized within an organization.
Webcast: Calculating the ROI for XML and DITA topic-based authoring
In this webcast, Sarah O’Keefe discusses how to calculate the return on investment of an XML/DITA implementation for technical content.
If you are considering XML and DITA, but are trying to figure out whether you can justify the cost and effort, this session is for you.
2011 predictions for technical communication
Predictions time! First, let’s review the 2010 post: cloud-based authoring begins to replace desktop authoring, increased adoption of XML alongside more sophisticated justifications, social media, collaboration, important new terms (content strategy [yes!] and decision engine [huh?]).
I’m not sure why I thought “decision engine” was going to take off, because it didn’t. Onward to 2011…
The state of structure, 2011
Happy New Year!
In early 2009, we did a rather extensive survey on structured authoring. We asked about plans to implement structured authoring, existing implementations, biggest mistakes, and the like.
Once more into the breach…
Back in June, we hired Ryan Fulcher as an intern. Ryan has done great work, and has now been promoted to full-fledged consultant. Congratulations to Ryan!
The bad news, from my point of view, is that we now must look for a new intern.
