Currently WebControl supports both online and offline help. When the user clicks Help->Online Help, it brings up a new tab that takes the user to a website that hosts the help webpages. When the user clicks Help->Offline Help, it brings up a modal window (window that overlays the screen) that displays the help webpages. To make this work, a single set of help pages has been created. The online help webserver references these pages off the github repository where all the files/source code to WebControl is stored. The offline help “includes” the pages in the release files. This way, we don’t have to maintain two sets of documentation files.
With that said, we are looking at ways to add more content and edit existing content, in a collaborative manner. The problem right now is that the current system of using one set of files is a cumbersome and requires that things be done in a precise manner and the only way to know you got it right, is to do a bunch of testing. I spent more time fixing formatting issues between offline and online help than I did doing actual documentation.
What I would like to propose (and get feedback on) is to bifurcate the help system by using a separate set of files, leaving offline help being basic instructions that don’t change often and online help being more “expanded” help. This would allow us to do more collaborative work on the online help system and people don’t have to be developers or markdown experts to create it. We could also add links in the offline help files that point to the online help pages where users can obtain more info on a topic.