emagin contacted me saying some here are interested in creating docs. A friend and I were slowly working on some in a Wiki. Anyone is invited to join in if you want. I've modified the script to take a database back-end to allow others to use it as well. If you contact my friend
with what username and password you would like to use we'll add you if you've been a registered contributing member here. It actually can be opened up completely, but since we're giving admin privileges we're restricting access to logins this way.
To address some of the concerns here. There are a number of free and commercial editors one can use to create documentation some of which are definitely better than Wikis. The main benefits of a Wiki though are: 1) it's a tool for collaborative work, 2) it's far easier than many of the other products for the average person to learn, and 3) almost all of them are completely free. They are in no way a high-end help document creator and do have limitations.
The one we set up is PHPWiki. The reason we chose this one was unlike many of the others, it allows pages to contain plain text, any HTML tags, as well as PHP code, or a mixture of all three. Can you insert graphics? Yes. All it requires is placing the URL inside square brackets like this [http://www.domain.com/graphic.jpg] or use HTML tags like this:
PHP Formatted Code
add any tags you want here <<<<
add any tags you want here <<<<
Can it have a collapsible menu? Yes...but it requires writing a PHPWiki plugin to give this effect because none of the default plugins do this. The TOC for one document could indeed end up several pages long just like in any book. It could also be written where the upper TOC is high level and each section displays the sub-menu of its content instead. Alternatively, one could create the same effect that RoboHelp has using frames with a javacript menu. Such menus are great, but they tend to slow down (loading and changing) significantly as the number of links it has to deal with increases. Also, most js menus do not work cross-browsers or in those with js turned off. In which case, they will also appear as a very long TOC.
Why are so many Wiki's practically all text? Because most are totally open to the general public to freely post on. Many of them also do not have the capability to handle HTML/PHP or severely limit this access due to security concerns just like we do on Geeklog. I doubt you'll find many, if any, media-rich Wikis because they are mainly used for the very simple markup language for collaboration purposes.
Webpages are literally filled with HTML tags which makes it very hard and slow for the average human to read and edit. Wikis were designed with a simple language to make this faster and easier. They were also developed before any WYSIWYG editors were made for webpages. They were never created with the intent to develop feature rich HTML pages though a few today will handle the tags. Those who have used Wikis for documention usually don't insert graphics. I don't know why since many have this capability and it definitely aids understanding. Then again, a lot of docs are not written at the level of the intended audience. The one we're using can have literally anything that can go into an HTML page but to do so requires admin access. The more you stick to the simple markup though, the easier it will be when you or someone else goes back and reedits.
By all means, please take the time and do a search to see if you can find something better that doesn't cost a lot of money and can be used by multiple people or even develop something GL tailored. We're not attached to PHPWiki. It's just a tool to help put info together. A Wiki is definitely a poor cousin to many editors, but I'll tell you that hasn't stopped different people from trying to suck up the entire site almost every day (and thus get banned as well) even though it's not anywhere near complete.
If anyone here is guilty of doing such activity, please stop because this is one reason we haven't gone faster. After the doc is in a somewhat decent shape, it will be made available for download.