Building my help file with Dr.Explain was a pleasure to do.  It is easy to tell that the producers of Dr.Explain either regularly make help files themselves, or they listen very well to their customers and add requested features that are real productivity boosters.  In terms of things that boosted my own productivity, I lost count, and this article doesn't come close to listing them all.  (See Creating an HTML Help File with Dr.Explain for more details of how this product helped me create a fine, professional-quality product.)

 

Despite a small number of things I ran into (see Things That Could Be Improved, and Wish List sections above), the productivity boost I experienced and amount of things that are REALLY RIGHT with this program FAR outweighed any annoyances.

 

I also found that since I studied the Dr.Explain help file in depth, once, and practiced each thing I felt weak in, that I walked away from this project with a FULL knowledge of what Dr.Explain is capable of (at least what was documented in its Help file), which means next time I need to use it (which might be in 3 months or 23 months), it won't take me long to come back up to speed with it.

 

And by the way, the Help file that comes with Dr.Explain was created in Dr.Explain, and I found I was able to use it to get productive using Dr.Explain in a very short amount of time.  This in itself is another very nice compliment to Dr.Explain, making it that much easier for a new person to "train" themselves how to use it with the Help file.  I was pleasantly surprised by this, as it is not common to find application Help that is so clear, concise, and easy to use!  In addition to the high quality Help Files and technical documents Dr.Explain allows me to create, the fact that I was able to come up to speed quickly with it was one of the factors that makes it, in my opinion, an ideal pick among the Help-Authoring software packages available.