Hi, Mike,
The thing is, I wrote a topic for each inividual screen,
which is what I'm used to. There is no "master" topic that can be
used to cover all screens (of which there are over 100 for the
application I've been assigned).
One help screen/topic would work fine, if the user were only
allowed one screen at at time. But I'm being asked to accommodate a
situation where there are multiple, unrelated screens displayed in
one window, and there is only one help button on the menu bar at
the top.
If the screens were related, it might make a difference, in
that the help option could open a "master" topic that would in turn
offer the user a logical menu of topics from which to choose. Alas,
this is not the case.
So, the only solutions I can see are:
(1) Request that the programmers go back and add a HELP
button to each individual screen. The user will click the help
button for the screen he/she wants help for. As for the help button
on the menu bar at the top of the application, that would be
reserved for System-wide help only, having a TOC and keyword search
capability. Don't know how happy the development team will be with
that suggestion. Not that I think it would be hard to do, but with
about 1000 screens spanning numerous applications, it's still work.
(2) Forget about asking them to add a Help button to each
individual screen. Just don't offer context-sensitive help.
Instead, set up the help button on the menu bar for System-wide
help only, providing an introduction, TOC, and keyword search
capability. (Something along the lines of what you get when you're
working in Robohelp X5 and you click Help.) It's not as user
friendly, but it would be better than nothing.
(3) Offer field-level help. But the problem with that (other
than the fact that I've never done it before, but how hard could it
be to figure out?) is that I don't have lots of time for this
project and there are many elements on each screen. I see that as
being unacceptably time consuming.
And can you even do field-level help in Webhelp?
Lori