I wonder if tech writers are, in general, involved with FAQs.
They should be. If there's going to be a FAQ, it really helps if it is
well-written, and it is probably a good idea to have it follow the
same conventions and use the same terminology as the main
I think that FAQs come from two places: support, and "development"
Unfortunately, some come from marketing. That might be OK if
they were genuine, answered real questions one might have
about the product. Usually, though, they are answering questions
marketing would like customers to ask. These so-called FAQs are
utterly dreadful and have driven me away from some products.
Also, some come from the notion that a FAQ is just a standard
part of a documentation set. The writer, developers, support or
management might drive that, but in any case it is a widespread
Here's a FAQ I wrote that I think is a decent example:
Zhuhai, Guangdong, China
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
Doc-To-Help includes a one-click RoboHelp project converter. It's that easy. Watch the demo at http://www.DocToHelp.com/TechwrlList
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com
To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.
RE: FAQs: From: Joe Malin
Search our Technical Writing Archives & Magazine