[TYPO3-hci] Documentation for Projects
Søren Schaffstein
soeren.schaffstein at media-lights.de
Thu May 18 17:32:43 CEST 2006
And exactly here lies the problem. We're not talking about "possibility"
- in this newsgroup it's about "usability".
Person A creates notes on every page where there is something to
explain. Person B creates on page full with notes - but you need to find
this page. Person 3 creates a hidden page somewhere and places a content
element with all the info there.
So in my eyes it would really help to have some kind of BE-module which
could be something like the help which keeps this system documentation
at one place for every installation.
Maybe I can build a sample screen of what I have in my mind to make the
idea clearer? Anyone interested?
Søren
Johannes Reichardt wrote:
> But what would you specifically need that is not already there? You
> could make a note in the user area or have a dedicated page for
> developers that is hidden for the public.
>
>> 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
>>>>
>>>>
>> _______________________________________________
>> TYPO3-team-hci mailing list
>> TYPO3-team-hci at lists.netfielders.de
>> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-hci
>>
>>
>
More information about the TYPO3-team-hci
mailing list