[TYPO3] Documentation nightmare

Dan Osipov dosipov at phillyburbs.com
Sat Mar 15 00:09:39 CET 2008


+1 for PDF.

Also, will the web documentation be rendered from OO files? Just so that 
everything is always up to date, no how the user wants to read the docs

Dan

Dmitry Dulepov [typo3] wrote:
> virgil huston wrote:
>> OK, this is a good discussion and we need to come up with a good way to
>> work. Personally, I do not like the wiki to actually work on docs, but 
>> only
>> to manage the docs. With the wiki, when things are edited, etc., 
>> afterwards
>> someone still has to put them into OOffice, format them, etc. This seems
>> like a waste of time. I would use the wiki to manage and organize and
>> discuss, but the actual manuals (or section being done by separate 
>> authors
>> if appropriate) should be written and edited in OOffice, as long as OO is
>> the standard. We need to go beyond OO, I think, I have clients where I 
>> have
>> to convert the docs to PDF for them, they will not usee OO. But OO as a
>> writing standard is fine.
> 
> For downloading: OO + PDF. PDF is much easier to read from screen (no 
> editing marks, etc).
> 


More information about the TYPO3-english mailing list