[Typo3-documentation] Document guide

[Johannes Reichardt]

Hi Peter,

>
> Fine with me.  ;-)
> I hope you have notised that right now you and I have different goals 
> with the wiki:
>
> You want it to be a place where newbies can find (all?) documentation 
> for Typo3, and...
>
> I want it to be a project place where we can restructure and create 
> new documents for both newbies and experinced Users/editors, 
> Administrators and Developers.

Well thats different point of view, in fact. I thought its a "fresh" 
wiki which should grow by time. Therefore i thought a very intuitive 
surface would make sense. In fact it should be better then the rest of 
the documentation because there is "real-life" contribution that makes 
the information more valuable than somewhat dried out references made by 
one person at a certain time.

Also i wouldnt make any distinction between expirienced and 
unexperienced if it goes to navigation. Usability (which includes 
navigation) can´t be newbie-friendly enough, to my opinion the structure 
right now overhelmes most people with categories (is it fe or more be?) 
and it doesnt focus on real-world-problems. Someone who needs that 
information might want to have a link first "what is the difference of 
the be and the fe, should i look in troubleshoot section (hell!) or 
should i look in the reference?".

> But, you get us wrong!
> You seem to have ONLY newbies in mind. And we want to focus on 
> newbies, but ALSO produce documentation for other Typo3 users.
>
> If you can´t accept a structure that also take in consideration other 
> users than newbies, I belive the Main page is not the place for your 
> structure suggestion...
>
> But, of course, this is only my point of view.

Sorry for popping in and shouting "NEWBIES" all the time - i had some of 
these discussions before and since i am in a bad circumstance of not 
having the time to make all i complain about i tend to get misunderstood.

Just to make this clear: Personally i think the focus on newbies would 
solve many problems without discussions - just because its about 
simplicity and not well-thought programmers stuff. By the way, most 
other projects which focus on many people (php etc...) have supersimple 
navigation and lots of helperfunctions (like php.net/function etc...) - 
thats that kind of stuff which helps everyday and typo3 lacks of in many 
ways.

- Johannes

PS: just got the "you have to set the wiki up first" message again, 
right on wiki.typo3.org ;)