This content has been marked as final. Show 4 replies
Doh! I forgot to explain why you need to look at them. RoboServer will enable user group access. It is described in the Reviewer's Guide.
"I am using RoboHelp 6 at this time, and am looking at the use of Merged WebHelp (on www.grainge.org), conditional topics, and RoboHelp Server. Can anyone provide some insight as to the benefits/risks of each of these? Also, I would like to be able to create separate indices for each subproject."
We run a 7-writer, 42-project merged WebHelp environment (with Peter's recommended structure). The output gets published, project by project, and requires no major "build" of the entire help.
Based on your user-privilege scenario, I'd eschew conditionalizing topics in favor of organizing your merged help into separate projects for each of the user responsibilities. Then, your developers would set up access privileges by user/by folder, allowing for relatively painless growth (conditionalizing your anticipated "25 or 30" user roles would definitely drive you into a different career, perhaps sorting items in a recycling center?). You might also ensure that each project is assigned to an individual writer, thereby negating the need for source control. We simply use Karen's Replicator, a free tool, to sync our projects daily from our local machines to a dedicated server for storage and backup.
The RH Server is used to house WebHelp Pro output, which allows for more advanced searching and for topic "hit counts." However, I believe that those features are only available in those instances where the WebHelp Pro output is actually being accessed from an RH Server (if you were hosting the help on your company's web site, or if your users bought an RH Server license for their site).
Thank you both for this information. I will investigate.