#31973
Choosing a Help Authoring Tool 
Discusses in detail why you might want to consider a specific tool for help authoring.
James-Tanny, Char. Helpstuff (2004). Presentations>Documentation>Software>Help
#29918
A weblog for writers of documentation and users of Help Authoring Systems.
#31974
Several years ago, someone used the term WYSIOP (What You See Is One Possibility) when talking about the RoboHelp HTML editor, because what developers saw in the editor didn't usually match the results. I had what I thought was an absolutely brilliant leap of logic ;-) a couple of months ago when I realized that today's WYSIWYG (What You See Is What You Get) editors are really WYSIOP, because the results are determined by whatever layout template is assigned at the time the results are viewed.
James-Tanny, Char. Helpstuff (2006). Articles>Web Design>Document Design>Adobe RoboHelp
#20034
Using the Single-Source Wizards in RoboHELP 2000 for WinHelp
HTML Help is the Windows Help standard for 32-bit operating systems (for example, Windows 95, Windows 98, Windows NT, or Windows 2000). Your users must have Internet Explorer installed on their systems (or at least the necessary core components).
James-Tanny, Char. HelpStuff (2000). Articles>Content Management>Single Sourcing>RoboHelp
#32042
Back in 1998, I defined topics as "'chunks' of information in a Help file that answer one question or provide focused, specific content." Ten years later, I typically use the same definition. However, there have been some changes in how those "chunks" are developed.
Helpstuff (2008). Articles>Documentation>Writing>Technical Writing
