Step 4 -- Provide Your Application with Context Sensitive Help
I left adding context-sensitive help to my application until the document was virtually completed and would not be further significantly modified. This is so that hopefully I would not have to do this step more than once. And indeed, I only needed to do it once.
Interestingly, once this step is completed, and linked to your application, you can still move the pages around and change the TOC hierarchy, and the application will still open the Help File to the same page, without you having to change anything. This made me very happy, because I actually did need to rearrange the TOC hierarchy in a way that moved the pages my application was linked to.
I refer you to my separate article on how to do this:
How to Add Context Sensitive Help to Your Application Using Dr.Explain
One thing I found very convenient is that it is often the case that certain pages should go into certain outputs (e.g. HMTL and CHM, but not PDF), or simply should not appear at all EXCEPT for context sensitive help from an application. Dr.Explain provides a way to manage these scenarios with only a few clicks.
If you want the page to simply be PRESENT in a CHM or HTML output, but not be accessible by the user via the TOC or via internal links, then select the page in question in the TOC tree and either hit the Del key, or right-click it and select "Hide/Show" to hide it or make it "visible" again.
If you want the page to only go into certain outputs but not others, when the page in question is selected in the TOC tree, the Properties window displays a list of which outputs (HTML, CHM, RTF, PDF) that page will be sent to under the heading of "Export to". It only takes one click to turn them ON and OFF.
