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.
I'm interested in getting information on Application Notes, also called
Product Profiles. I checked the archives and there were two messages on
this topic two years ago, but I would like more feedback if possible.
@ How technical should the application note be? ie. should I include code
samples, flow charts, architecture diagrams, etc.
@ How do I make an application note different from a white paper, esp. if
the white paper also identifies applications for the product? I guess the
question is actually, how is an application note different from a white
paper?
@ Should an application note be part of a product package, or should it be
designed to stand alone?
@ At what point does the user receive an application note? After the
brochure? After the white paper? After they buy the product?
@ Is it okay if the application note has a distinct sales spin?
@ How "desktopped" should it be?
@ If the product has not yet been tested in "real world" situations, is it
acceptable for the application note to be based on our best guess about real
world applications?
Thanks for your input and suggestions.
Cheers,
Rowena rhart -at- intrinsyc -dot- com
---------------------
Rowena Hart
Technical Writer
Intrinsyc Software, Inc. http://www.intrinsyc.com
