Currently we are generating the documentation directly from the source, and this is typically done after we add or change commands (for our own reference). It sounds like the solution, minus correct terms, is to generate PART A which is this core documentation dumped from the latest build of AGK. PART A is then uploaded as a Wiki update, which joins onto an existing PART B. PART B is all the comments, code, advice, tips that relate to each command in the Wiki (not sure how this can be done per command page, advice welcome).
For each update release, we snapshot the on-line Wiki (PART A + B) which becomes our off-line help system which is part of the latest update installer (instant local help). The same snapshot is uploaded back along with the updated installer to our on-line portal so the new commands/changes are instantly available on the day of release thus retaining contributions of comments, code, advice and tips provided to date (the PART B stuff). Just like forum moderators, we would appoint trusted valued members of the community to oversee what goes into the PART B stuff to ensure it remains clean and relevant.
Does this sound like the right solution all round? Vote YES if you think I am talking sense, and NO if you think I am talking pile
I drink tea, and in my spare time I write software.