[TYPO3-hci] Documentation for Projects

[Søren Schaffstein]

I got your point, but that's all targeted at developers. How about 
end-users? Sure I can create a page in the sitetree where I place how-to 
information. But wouldn't it be nice for an editor to open a 
documentation page and look up what is important in e.g. the news 
creation process? How about if the chief editor is ill and someone needs 
to take over for just one or two days?


Søren

Johannes Reichardt wrote:
> i don´t think that is a good idea - i´d rather remove complexity and 
> make current things more intuitive than adding a new "can do" layer that 
> is based on the good will of the developer if he uses or not.
>> I'm currently working on a TYPO3 installation we took over from 
>> another company and it's really hard work to find all neccessary stuff 
>> and see how everything was created.
>>
>> Therefore a nice tool could be a project/system documentation tool 
>> which consists of an enduser and a developer part. So if someone opens 
>> a project after some time and is not sure how this or that should be 
>> done / was ment to be done it can be found in this system 
>> documentation. Especially for developers this could be really helpful 
>> since TYPO is so powerful that many things can be done in more than 
>> one way.
>>
>> What do you think?
>>
>> Søren
>> _______________________________________________
>> TYPO3-team-hci mailing list
>> TYPO3-team-hci at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci
>>
>>   
>