We might have another good alternative option to the wiki (maybe easier and more flexible): use a github repo for all the documentation pages in makedoc format, and have external export batch script to export them in HTML, PDF or whatever format.
I would be able to write most of the reference documentation, but would probably let the dictionnary be written by the community. The githun repo would allow for everyone to contribute while being filtered by one or several managers.
Now, where is that new version of altme that uses git for file sharing and just hides all the details...
AdrianS: Github Pages uses Markdown format, they have no support for makedoc.
Gregg: the Red dictionary could be displayed in different ways, the treeview (unfolded like for clojuredocs or navigatable like in the Sensha demo) is one option, another is displaying it like REBOL's one:
Anyway, the dictionary is a not the "reference documentation" (think REBOL/Core manual) which should be the first focus.
I'm also adding other features we should have for Red docs: - search field: a true local search engine, not a wrapper on Google search. - versioning: ability for users to consult any previous version of the docs. - a simple way to track changes in the docs.
For now, I would just link the docs from red-lang.org and host them on static.red-lang.org which points to my own server.
In a few months, when bootstrapped Red will be complete, I would like to move all to a new, more appealing web site. I might use a github repo for managing the static parts of the web site. I would also move the blog to WordPress or anything else than Blogger.
About Git, it is not that complicated, you just need to learn a few (2-3) usage patterns to be able to install/update your local repo and submit a change. Maybe someone could provide a simple Red-repo-oriented tutorial using TortoiseGit and command-lines for those basic usage patterns?
GitHub Pages also serves up static html/css/js. Still, if you couldn't use any server-side scripting, you'd need to pre-generate the html and I guess you wouldn't want to do that.