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.
It sounds like what RoboHelp is providing you with is a "mini-Project"
interface for tracking progress and completeness. That is not the same as a
documentation plan. You need both the plan and a means of tracking your
progress on that plan. Otherwise one or the other alone isn't worth as much.
Bill Swallow
wswallow "at" nycap "dot" rr "dot" com
::: -----Original Message-----
::: I am working on developing an on-line Help system using RoboHelp.
::: I see that RoboHelp has a feature that allows you to track topics
::: individually. (You can keep track of which topics are
::: complete, which need
::: to be reviewed, generate project status reports, etc.)
::: Do RoboHelp users find this feature sufficient for tracking
::: topics, or do
::: you additionally (or alternatively) use a written
::: documentation plan?
