From toilets to techcomm: tallying tool risks
I’m about to replace an old toilet, not-so-affectionately nicknamed the Lazy River.
I’m about to replace an old toilet, not-so-affectionately nicknamed the Lazy River.
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?
So, you’ve decided to move to a DITA-based workflow. Before you convert your existing content to DITA, consider these five tips, which encompass both big-picture and coding-specific issues.
In this webcast recording, Alan Pringle discusses the challenges of ebook distribution and how Scriptorium has addressed them when selling EPUB and Kindle editions. Topics covered include:
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.
Every department has its resident tech wizard: the maintainer of the templates, the DITA Open Toolkit, the wiki, and so on. What happens when that wizard flies off to a new kingdom?
In this webcast recording, Simon Bate discusses the pros and cons of using the DITA Open Toolkit. Topics include localization, automation, open standards, and plugin architecture on the pro side; plugin architecture, PDF configuration, open standards, and documentation on the con side.
Reuse and automated formatting are the most common justifications for XML, but recently, we have heard a new reason from several customers: rebranding.
In the world of superheroes, technical writers could just slide down a pole or do a clandestine spin to transform themselves into DITA technologists. Of course, nothing is that easy, so what does the transformation from tech writer to DITA superhero really require?