Stay current with the latest in tech comm
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 5,000+ subscribers

Stitcher radio

Search results

Upcoming event:
I'm giving an API documentation workshop in Los Angeles, California, on January 23, 2020. Check it out on EventBrite and register today to receive a $100 early bird discount.

PDF still trumps browser-based help?

by Tom Johnson on Mar 19, 2015 • 0 Comments
categories: technical-writing

In the Skills and Technology Survey 2014 by WritersUA, it appears that PDF manuals are the most common deliverable:

Support for manuals in the form of PDF (77%) is at the top of the list as the most valued technology component. Using PDF as a delivery format has become a staple in our documentation sets. PDF files can be delivered on an installation CD or via the Web. In the past, this technology was mainly used for legacy print documents like user guides, and also for supplemental white papers and troubleshooting information. Today we find many organizations using PDF files as the primary distribution format for product documentation.

Print is still of use to 1 ot of 5 respondents which is a healthy number. ePub and Kindle are likely to grow in usage, but the UA community doesn't seem to have found them exceptionally useful yet.

The use of browser-based Help (73%) continues to be very popular with our respondents placing it second. The lure of displaying content in a web browser window seems to offer enough positive value for us to favor it over more feature-rich, platform-specific proprietary Help systems. This form of content delivery uses standard and non-standard Web technologies to deliver Help content through Internet Explorer, Firefox, Safari, Chrome, and other browsers. Implementation strategies run the gamut from using basic HTML pages to proprietary solutions, such as WebHelp and WebWorks Help, to complex renderings employing custom JavaScript and HTML5/CSS.

This actually blows my mind. I was talking with someone from a large multinational company at tcworld India last week (I can't remember exactly which company, but it was one of the big ones), and she explained that they purposely do not create PDF manuals for a number reasons -- mainly, they grow quickly out of date. In an agile development shop, how can you give users a PDF that will be out of date in a month?

I'm not looking to reproduce the extensive discussion on previous posts about PDFs, or suggest usability articles discouraging PDF. As long as 77 out of 100 tech writers continue to produce PDF manuals, I think the transition from paper to the web will continue to be a major paradigm shift for the tech comm world.

follow us in feedly