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.
Subject:RE: Type of documentation? From:"James Barrow" <vrfour -at- verizon -dot- net> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 29 Aug 2006 06:46:49 -0700
>Generously Written On Behalf Of Chris Orr:
>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
>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
>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,
>feedback 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?