From: Phillip Gawlowski <cmdjackryan@...>
Date: 2011-08-03T02:40:56+09:00
Subject: Re: Documentation Improvement Proposal

On Tue, Aug 2, 2011 at 6:36 PM, Chris White <cwprogram@live.com> wrote:
>
> * Recommendations for the content management system

Given your requirements, TikiWiki[0] would fit quite well, and allows
for quite a bit more (From issue tracking, to automagically generating
a book-like PDF, multilanguage support and tagging are baked in and it
provides publishing stages [writing, editing, publishing], as well as
comments).

The downside is that it requires a relatively beefy host (Loads of
memory for PHP, and a long running time for the scripts).

Otherwise, DokuWiki[1] isn't resource hungry, and operates on plain
text files, which, when using the markdown plugin, should allow
transformation into other formats via pandoc[2] that can be printed
easier or read on a mobile reader when internet access isn't
available.

If RDoc generation is a hard requirement, pandoc can also be fed plain
old HTML and transform that into PDF, ePUB, &c. if multiple formats
are desired.

> * Volunteers to help with writing a tutorial revolving around the Koans
> ( this can sit on GitHub until the content management system goes up )

While not based off of the RubyKoans, feel free to steal my AES crypto
tutorial from [3] for a tutorial section on Ruby, or to inspire a
RubyKoan or two.

[0] http://info.tiki.org/Tiki+Wiki+CMS+Groupware
[1] http://www.dokuwiki.org/dokuwiki
[2] http://johnmacfarlane.net/pandoc/
[3] http://rubylearning.com/blog/2011/07/18/cryptography-or-how-i-learned-to-stop-worrying-and-love-aes/

-- 
Phillip Gawlowski

phgaw.posterous.com | twitter.com/phgaw | gplus.to/phgaw

A method of solution is perfect if we can forsee from the start,
and even prove, that following that method we shall attain our aim.
              -- Leibniz