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: How do I document vaporware? From:"Downing, David" <DavidDowning -at- users -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 28 Jan 2009 13:06:31 -0600
From: "Sarah Stegall" <sstegall -at- bivio -dot- net>
Subject: How do I document vaporware?
Having spent half a week taking all references to a certain feature OUT
of our software documentation, I am now informed that these references
are "placeholders" for future development. This means that when our
users (other software developers) browse through the command line
interface or the help menu, they are going to find undocumented commands
(that don't currently do anything anyway).
There's no telling when these "features" are actually going to be
implemented (software design plan? We don't need no stinking plan...).
What would be the best way to mention these in user documentation? I am
afraid our users will be very confused when they happen across
undocumented commands. Has anyone else had to deal with this? Thanks for
What I'd do is find some dignified way of describing the situation that involves the word ?future? - ?These commands will become available in the future,? or? These commands are reserved for future use,? or some such thing.
Interesting how an occasional part of our occupation is to document something stupid so that it sounds like it made sense to do it that way.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-