The future of computer book publishing
Computer book publishers have always struggled to keep up with software releases. The rise of cloud-based software with incremental releases requires new thinking.
Computer book publishers have always struggled to keep up with software releases. The rise of cloud-based software with incremental releases requires new thinking.
We read Tom Johnson’s post on Structured authoring versus the web with some dismay. Tom is a persuasive, influential writer, but his article misses the mark in important ways.
In this webcast recording, Sarah O’Keefe, Scott Abel (The Content Wrangler), Race Bannon (Oracle), and Paul Perrotta (Juniper Networks) discuss the state of the technical communication industry.
Given the choice between an inexpensive writer with a limited skill set and a professional technical communicator, which should you choose?
One of the most important issues in technical content is to establish a single source of truth for technical data. More often than not, our workflow assessments uncover multiple sources of dubious accuracy.
Reuse and automated formatting are the most common justifications for XML, but recently, we have heard a new reason from several customers: rebranding.
Deciding on a content model is a critical step in many of our projects. Should it be DITA or something else? The answer, it seems, often has more to do with our client’s corporate culture than with actual technical requirements.
In this webcast, guest presenter Chip Gettinger of SDL discusses key success factors for component content management systems.
Content velocity is the speed at which we create and produce content, the speed of the publishing process itself, and the speed of change in content requirements—what we need to produce and the delivery mechanisms.