[Typo3-doc] Re: [Typo3] My experience with Typo3 and a lot of questions.

[Peter Kindström]

Hi Stefan,
> But more META-documentation like the introduction, i.e. where to start 
> would probably be good. Examples:
 >
> Which docs to read and videos to watch to become a kick-***-typo3 
> extension developer: doc1 [about blabla], doc2 [about YADABLABLA], 
> doc3[about YADABLABLA2]
> 
> Which docs to read to become a master BE editor
> 
> Which docs to read to become a superior BE administrator creating BE 
> groups and editors
> 
> Which docs to read and who to contact to become a core developer
> 
> Which docs to ...

This have been discussed a little in the doc newsgroup too. I 
call it "Documentation guides". It could be a list/page per 
subject and involve links to both documents, videos, FAQ/HoqTos etc.

But first of all I think the whole documentation structure 
should be formed a little as a guide, based on skill level:


1. You start with the *Getting started* section

a) There you get a *Typo3 Introduction* and learn what Typo3 can 
do and not. You also learn where to find more informaton, and 
about the general concept of Typo3.

b) Now you are ready for the *Typo3 Basic Installation Manual* 
where you learn about different packages and how to set up your 
first web site on different operating systems.


2. Then you are ready to be an *Editor*

a) There you read the *Typo3 Editors Manual* and learn 
everything about adding, editing and deleting pages.

b) If you want details, you just look in the *Typo3 Editor 
Reference*, which also is included in the backend manual module.


3. Next skill level is to become an *Administrator* of Typo3

a) There you should start with the *Typo3 Administrators Manual* 
where you learn the basics about TypoScript, Templates, 
Extensions, Security etc.

b) Later on when you want to look something up, you go to the 
*Typo3 Administrators Reference* where you find details on how 
to use Multiple domains, Encrypted email address, Alt text for 
images etc.

c) And if you want to know how to do a thing in a backend 
module, you look in the *Typo3 Backend Modules Reference*.

d) Extensive topics/subjects have their own documents, like the 
*Typo3 User Management Manual*, *Typo3 PHP Configuration Manual* 
and *Typo3 Digital Asset Management (DAM) Manual *

e) Now you are well prepared for making your own web design. You 
use the *Typo3 XML Template Manual* to learn how to use 
TemplaVoila for making good looking templates.

f) You learn about the details of this TemplaVoila concept in 
*Typo3 Flexible Content Elements Manual*.

g) ...


This is as far as I have come until this day. There are still 
some Admin documents and all Dev documents to organise...  ;-)

And I havn´t mentioned that many of the documents have to be put 
together from different other documents. Some sort of a big 
documentation restructuring.


--
/Peter Kindström