Gone with the width: what’s the optimal length for a line of text?
When it comes to a line of text, how long is too long? And do the rules for text column width change when content is rendered on different devices?
When it comes to a line of text, how long is too long? And do the rules for text column width change when content is rendered on different devices?
Some thoughts on technical communication, content strategy, and the state of the industry at tekom/tcworld 2012.
A few weeks ago, I described some of the issues we faced in producing a PDF of Content Strategy 101 from DITA sources. Time and space didn’t permit me to finish the list of changes out. Now I can.
In which we uncover some unpleasant realities about distributing ebook editions.
In which we jump through flaming hoops for EPUB and Kindle.
In which we bend PDF publishing to our will. Eventually.
In this webcast recording, guests Alyssa Fox (NetIQ) and Toni Mantych (ADP) discuss their differing DITA implementation decisions.
In which we are boxed in by the limitations of DITA indexing support.
In which we build assorted graphics and develop style guidelines.
In which we develop narrative content in a modular architecture.
Content migration from format A to format B is a challenge in the best of times. And then there are the worst of times, like the depressing situation in this message (published with permission from the author):
When selecting authoring and publishing tools, there is an unfortunate human instinct to cling to the familiar. This ranges from a slight preference for the tool currently in use to “You will pry this software from my cold, dead hands.”
Until I started working at Scriptorium, my educational and work background was in information and library science.
The mantra of XML is that you separate content from formatting. Authors do content; formatting happens later. During a panel discussion at last week’s (excellent) UA Europe conference, I realized that this is only half the story.
For remote work, file management in the cloud is way easy. Other methods, not so much…
When I started at Scriptorium a year ago, I knew almost nothing about tech comm. I knew what technical content was, having used it many times, but I’d never really thought about how it was produced.
The batch publishing paradigm is deeply ingrained in technical communication, and breaking out of it is going to make the transition from desktop publishing to structured authoring look easy.
It can be a mightily sucktacular experience when you discover what other people think technical communicators do.
We all know that Lorem Ipsum is not your friend. But sometimes, even sample content fails.
In this interactive session, technical communication experts Sarah O’Keefe, Nicky Bleiel, and Tony Self give their opinions about important current topics in the industry.
The stereotypical technical writer working in isolation is an endangered species—if not already extinct.