> On Thursday 17 November 2011 12:17:00 pm Timothy Pearson wrote:
>> Overruled. :-)  The consensus here (which I agree with) is that no
>> markup
>> languages are needed or desired.  This documentation could potentially
>> grow to the size of a small book--can you seriously even imagine trying
>> to
>> edit that for clarity, let along grammatical errors, without a word
>> processor?  There is a right tool for the job, along with a bunch of
>> wrong, but workable, tools.  Let's use the right one!
>>
>> We will use the flat ODT format in GIT.  I will work on getting
>> automatic
>> builds both to "real" document formats (PDF, PostScript) and to HTML.
>> Help is welcome here; basically I just need the command line to pass to
>> LibreOffice to make it spit out such documents, especially on the HTML
>> end.
>
> As long as there's public read access on the web site, that shouldn't be a
> problem. There was a comment earlier that people won't want to learn (or
> won't understand) version control, so making it downloadable in a browser
> without a "git clone" is desirable. If that's possible, I'm all for using
> git
> for the manuals.
>

Quite easily done.  Example:
http://git.trinitydesktop.org/cgit/tde-packaging/tree/README.GIT

Tim