[TYPO3-hci] The Constant Triptichon

Cate & Peter catepeter at optusnet.com.au
Thu Jun 22 13:00:39 CEST 2006


>> It seems to me that we have 3 people thinking that the backend
>> representing the front end visually in some manner is a good idea -
>> and one person (all due respect) obviously in disagreement,

>You can count me in, so it's 3:2   :-)

And me too, so its 3:3 :)

I'm a relative newbie, and yes for plain editing for content editors is a
good idea, but speaking from the point of view of someone who has worked
with 3.6, 3.7, 3.8 and 4.0 all in the last 6 months :S, the only thing that
has helped me is that the back end has remained predictable - its hard
enough to work out what is what, without that being changeable too.

>IMHO TYPO3 is meant to work as a Content _Management_ System not an
>Online-Dreamweaver-Clone. So editors are more like managers and less like
>designers.

Absolutely - exactly who I am developing for.

>This is why they are using a system like TYPO3, so they don't have to care
>about design and layout anymore, while they can concentrate on the
important
>stuff, which is writing and editing the content in a way they are used to.

Yes yes yes.

>But since TYPO3 is a modular and extendable system, a BE module extension
>would be a good choice to find out if this is what people really want.

I think this is the best suggestion yet... I wouldn't want to stop those who
feel it is needed, but I don't want this as standard just yet.


>IMHO a great number of the TV downloads is due to the fact that the
tutorial
>is called "futuristic template building" so maybe you should choose a
>similar wording to get better results ;-)

I have to agree. I have downloaded TV, and am working with it, and in fact
it is a great example of why I don't want any changes to the back end.

You say 'oh well, if the documentation covers the changes there will be no
problems'. Yeah, I agree. But the reality is, most developers of extensions
aren't TV users, and probably wont want this facility either, so the manuals
are not catering for that. Eg. I have been trying to implement a wiki in a
site - I have tried both TIMTAW and DR Wiki, and neither have been straight
forward becs they didn't document for TV. I have contacted both authors, and
neither are familiar with TV, so they have been unable to help me.

So here I am, a newbie, trying to troubleshoot problems that the authors
cant even work out. Doesn't make for good usability.

To expect anything to be new for a new type of back end is, I feel, a touch
unreal. Developers just don't have time, and sometimes motivation, to
document for half a dozen options.

Cate






More information about the TYPO3-team-hci mailing list