[Typo3-doc] Wiki people: who's on board now?

[Alex Heizer]

virgil huston wrote:

>On 11/3/05, Peter Kindström <peter.kindstrom at abc.se> wrote:
>  
>
>>Instead I spent some time during this summer to write down my
>>thoughts about the Typo3 documentation. I have now published it
>>for others to continue...?
>> http://www.infolagret.se/typowiki/index.php/Vision
>>
>>    
>>
>This is an excellent vision for TYPO3 documentation. Hopefully,
>whoever takes over the documentation team for TYPO3 as a whole (is
>this you, Alex?) uses it. Certainly, the US doc team should take it
>into account as things are worked out.
>  
>
I agree about the Vision page, and it seems like we have similar 
thoughts on making complete documentation, rather than competing 
documentation. I don't know if I'm taking over the doc team as a whole! 
I offered to help out and Peter handed it over! :)  ...but the idea is a 
whole team, and we have a good team here so far. It's been expressed 
that English is the official language for the documentation, and Kasper 
and Daniel have said in the past that it will be US English (the TYPO3 
English list even has as its default language 'English (USA)').

As for the format, we all need to be doing less work. Not that we should 
be sitting around on our hands, just that there is about a year's worth 
of full-time work in maintaining the documentation for a team of 10, so 
we need to come up with ways to make one action provide what is needed 
for everyone. I, personally, am not attached to any one single solution, 
nor against any solution, and I think we can come up with something that 
works for everyone -- document maintainers, developers, decision-makers 
in customer companies, content editors.

Is there a way we could make a developer extension that can edit the 
Open Office (or other standard document type) documents in real-time, 
like you can with a wiki, then save it again, that might be a way to 
unify a wiki's functionality for a developer, yet still provide a 
downloadable document for a customer, and keep the site navigation and 
management features that are T3's strong points. I am not a programmer, 
so I am expecting a reply something along the lines of "Are you crazy? 
That would take a year to program!" :) ..but that's what I think we 
need, more suggestions on how to get from here to there.

Alex