TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Eadaoin O'Donnell's company <<...is making a manual available for
downloading from a website. It will be downloadable in PDF format. As it
stands the PDF looks exactly like our printed manuals. I think that it would
be good if it looked a little bit funkier.>>
Why should it look "funkier"? (That is, what benefit does "funk" have for
the reader?) If you've designed something that works well in print, and the
PDF is explicitly designed to be printed, then don't change something that
works well. Technical Communication isn't about flash: it's about meeting
the needs of users. So if the printed version doesn't have glaring defects
that need "funk" to fix them, don't bother.
However, let's assume that the manual is intended for reading online. (If it
looks "exactly like our printed manuals", then that means you haven't
redesigned it for use on the screen, so I doubt that this is your intent.)
In that case, one very helpful thing you can do that you might be unable to
do in print (because of the cost) would be to use color. Use color to make
headings more recognizable, to make screenshots look more like the real
screens, to highlight notes and cautions, and so on: in short, to make life
easier for the user and make the manual more visually interesting, without
creating a garish sea of color. Next, take advantage of Acrobat's hypertext
features by making all the "see Chapter X" and similar cross-references into
hyperlinks, thereby adding value to the PDF version. That's about as jazzy
as you need to get.
"Technical writing... requires understanding the audience, understanding
what activities the user wants to accomplish, and translating the often
idiosyncratic and unplanned design into something that appears to make
sense."--Donald Norman, The Invisible Computer