The dawn of digital publishing
Is a week long enough to gain some perspective on the new landscape in ebook publishing?
Is a week long enough to gain some perspective on the new landscape in ebook publishing?
I’ve been thinking about how time affects communication. We have constant deadlines, some of which are easier to meet than others. But there are other ways in which time affects content strategy.
“What a curious feeling!” said Alice; “I must be shutting up like a telescope.”
And so it was indeed: she was now only ten inches high, and her face brightened up at the thought that she was now the right size for going though the little door into that lovely garden.
Lewis Carroll in Alice’s Adventures in Wonderland
It’s time for that annual exercise in humiliation known as the “review of last year’s predictions” followed by the “some people never learn” event in which I soldier on with new predictions.
You’ve never heard of the passion quotient? That’s because I just made it up. For example, if 5 authors report that they use Tool X and it is very important (5 on a scale from 1 to 5), then Tool X scores a perfect 5 PQ.
My cynical streak makes me very leery (and often weary) of what politicians say and do, particularly around election time. But an article about President Obama’s re-election strategy really resonated with me—mostly because it offers some insight into what we should be doing in technical communication right now.
Amidst all this discussion of content strategy, one common approach has been neglected. There’s little discussion of the no-strategy content strategy, even though this approach is probably the market leader.
Simple answers are appealing and are easy to remember. [Refrain from gratuitous political joke here, mostly.] But the real world is full of complex issues that are not easily reduced to soundbites. This also applies to technical communication and XML adoption.
You know you’ve had a bad travel week when you cannot wait to compose the complaint letter to the airline. But sandwiched between flight problems, I had a great time in Wiesbaden at tekom/tcworld 2011.
In my junk mail, the capital letters were screaming in bright red: WE’RE NOT ARTISANS.
A wise man once told me that the goal of marketing is to frame the question so that what you are selling is the best possible answer. In the world of tech comm publishing, the default question has been: “What tool should I use?”
My 2011 predictions post included a brief mention of curation analytics. This week, we have news from MindTouch that supports my thought that accountability in technical communication will increase.
Technical communication is in the midst of a huge transition from a craft/artisan model to an engineering model. Our consultants are the vanguard of this transition, and as a result, we are experiencing significant challenges in finding new employees.
This morning, I was among the many who received an email from Netflix CEO Reed Hastings. He was responding to criticisms that Netflix “lacked respect and humility in the way [the company] announced the separation of DVD and streaming and the price changes.”
The initial wave of DITA implementations is still building, but we are already seeing the early adopters move on to what I am calling DITA, The Sequel.
In addition to mixed column and copyfitting, the shift from desktop publishing to structured authoring may result in the demise of the traditional index.
Originally published in tcworld e-magazine, July 2011
In Europe before the 1450s, books were precious, rare objects and were usually copied by hand over a period of months or years. Johannes Gutenberg and his printing press changed the economics of information distribution.
Over the weekend, a friend showed me an episode of a reality show that featured some commentary by a “style expert.” This expert offered his advice while dressed in an outfit that would work well as a costume in a production of Oliver Twist (and that’s being charitable).
I’m having some trouble with the idea of “extending DITA” outside the world of technical communication. DITA is obviously important in the right environment, but should we be advocating the use of DITA for more and more content?
“Content is an asset worthy of being managed,” says Scott Abel. I agree that good content is an asset. Bad content is a liability. It’s time to talk about the shameful underbelly of technical communication.
My voice mail randomly bailed on me, and after much Googling and forum snooping, I still couldn’t get it to cooperate. I couldn’t log in, and no one could leave me a message. So, I went down to the Verizon store, intent on giving the (very friendly) folks there a piece of my mind.
Most of the DITA work that we do at Scriptorium is “full-on” implementation. That is, our customer decides to move their content from [something that is not DITA] to a DITA-based system. There are variations on the theme, of course, but nearly all of our customers are concerned about managing localization costs and increasing content reuse.
Ellis Pratt of Cherryleaf asks: How important is video to technical authors?
Graham argues you cannot afford to ignore video.
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.