[Typo3-UG UK] Documentation, planning, deligation (and more Typo3-UK meetings?)

[dan frost]

I think what we also need is a trouble shooting list for each area of 
the program.

For example, a TypoScript trouble shooting list would list ALL of the 
places that information can be found to help diagnos a problem. A 
similar thing for extensions, and so on, also..

dan

Stefan Onken wrote:

>Am Mittwoch, 30. Juli 2003 16:20 schrieb dan frost:
>
>  
>
>>I wondered if we could have a wish-list for the documentation,
>>and set a few goals.
>>    
>>
>
>well, I am still stuck with the simple question: "Where to Change 
>what ?".. I am quite sure, that _my_ solution to change the PHP 
>Code of extensions etc. ist not the correct one (but at least it's 
>working).
>
>ok, what about another approach ? We (You) do some example webpages  
>with different layouts (text menu, layer etc). On each website we 
>include the full Typo Template, explaination, etc. An example shows 
>more than 1000 words. So, it would be a complete online 
>documentation.. 
>
>I am missing for example complete references for Typo3 codes. There 
>is a German docu which is quite good (at least for the menu 
>section), but again lack of examples.
>
>cu
>stonki
>  
>