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.
Thanks to everyone who responded to my questions about the number of
topics per RoboHelp document, how to view which topics are in which
document, and how to organize the files.
Everyone who replied suggested that it would be best to consolidate to
fewer, bigger docs.
Other helpful suggestions:
*Use the RoboHelp Explorer to view docs and the topics they contain
(unfortunately you can't print this view).
*Keep context-sensitive topics together, separate from
non-context-sensitive topics. This helps when auto-generating map ids.
It also helps in the following suggestion. . .
*Compile the project and print the .hh file that corresponds to each
.doc file. (This works if you have map ids; those topics that do not
will not show up in this report).
*Use the Word Table of Contents feature.
*Chris Betterton (ChrisB -at- selectst -dot- com) has written a Word macro that
processes a single help source document and produces a report listing
topics, context strings, browse sequences, etc. as a table at the start
of the document.
