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.
My only concern with 'White Paper' is that generally those types of
documents are designed to be strategically convincing. I've only
created a few White Papers (2), but both described how our products
provide a solution to one problem in the market. I didn't discuss how
to use the product (i.e. nothing procedural).
My point of view is based primarily on Michael Stelzner's White Paper
From: techwr-l-bounces+chrism=docutechcorp -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+chrism=docutechcorp -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Nilesh Jahagirdar
Sent: Wednesday, August 30, 2006 4:10 AM
To: Zsuzsa Nagy
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Type of documentation?
While the documentation as a category seems to be a single project, I
you are looking at creating muliple documents focusing on different
If that's the case, go with Best Practices, and identify further
for the documentation: existing market review / analysis, Standards,
These categories could be based on content-wise focus, or on in what
the documents will see the light of day.
On 8/30/06, Zsuzsa Nagy <zsuzsa_nagy -at- yahoo -dot- com> wrote:
> What about calling these docs white papers?
> Zsuzsa Nagy
> > ------------------------------
> > Message: 2
> > Date: Mon, 28 Aug 2006 19:40:38 -0400
> > From: "Chris Orr" <got2940 -at- hotmail -dot- com>
> > Subject: Type of documentation?
> > To: techwr-l -at- lists -dot- techwr-l -dot- com
> > Message-ID:
> > <BAY20-F2CEB332F7D7CFC07D31FFBC380 -at- phx -dot- gbl>
> > Content-Type: text/plain; format=flowed
> > I am trying to come up with a good name for the type
> > of documentation I have
> > been working on lately, but I'm not getting very
> > far. Here's a description
> > of it.
> > Where our release documentation has a narrow focus
> > on specific products,
> > this documentation has a wide focus on tasks or
> > processes that span multiple
> > products. It is published independently of product
> > releases, to the company
> > knowledgebase and/or online magazine. There is a
> > possibility it could be
> > published in trade magazines. This type of
> > documentation is heavily informed
> > by research into best practices, standards, the
> > existing market, feedfback
> > from consultants in the field, and such.
> > Our manager calls this documentation "best
> > practices," but it's more than
> > that. What would you call it?
> > Thanks,
> > Chris Orr
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> WebWorks ePublisher Pro for Word features support for every major Help
> format plus PDF, HTML and more. Flexible, precise, and efficient
> delivery. Try it today! http://www.webworks.com/techwr-l
> Easily create HTML or Microsoft Word content and convert to any
> Help file format or printed documentation. Learn more at
> You are currently subscribed to TECHWR-L as
nilesh -dot- jahagirdar -at- gmail -dot- com -dot-
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> 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.
But hang on, there's music and art and things to tell you about yet!
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content