You can use WebHelp-generated files to create cross-platform application Help. Topics of this type:
Are very similar to window-level Help topics because they are files in HTML format that are created and authored in the WYSIWYG Editor.
Describe how to use applications at window- and dialog-levels. (Individual topics for each field or control are not supported.)
Do not require aliases or map files.
Do not use custom windows created in RoboHELP.
Require application developers to define how topics are launched (in the tri-pane browser or in their own window design).
Can be part of the entire HTML Help project that is generated as WebHelp output in uncompiled format.
Are tested manually with the application (not used with BugHunter).
Meet with your developers and identify all the dialogs and windows in the application that require context-sensitive Help topics.
Create a plan for developing these topics.
These topics can be part of an HTML Help project or you can create a separate project that only includes context-sensitive Help topics for the application.
Review the information about WebHelp and style sheets for information about browsers and topic formatting.
Author the topics in the WYSIWYG Editor. They can include formatting, images, links, popup links, and related topics controls. If your HTML Help system is intended to be viewed with Netscape Navigator, do not use Dynamic HTML or ActiveX controls such as splash screens and keyword controls (these are not supported). For further information, see Limitations of Netscape Navigator.
Spell check your topics, proof and edit them.
Generate the WebHelp output files.
Provide developers with a list of .HTM file names that you created to use with dialogs in the application.
Find out what programming tool your developer is using to create the application. WebHelp includes code samples your developers can use to add context-sensitive Help functionality to the application. For more information, see Using WebHelp as context-sensitive Help.
If you are testing the context-sensitive Help topics with the application, print a copy of the Topic Properties report and use it as a check list. As you open each dialog or window in the application and request help, mark the topics in the report and make a note of any that do not work properly. Let your developer know if any do not work because the fixes need to be made in the application (not in your Help topics).