[TYPO3-hci] The Paradox of Choice

[JoH asenau]

>> If your client wants an easy to use content management system it
>> doesn't necessarily mean that the cms should be easy to use out of
>> the box but that you have to restrict the features fitting for your
>> customers needs and knowledge.
>
> OK.. As far as I can tell from reading other posts on this list,
> maybe 3 of 10 actually takes the time to do this, because this in
> itself is a very cumbersome and difficult process.
> Why not reverse this, so that it's easy to use out of the box, and
> then add features etc if need be?
> Maybe I'm wrong on this?

IMHO you are completely right here.
As long as the features are not kicked but just hidden by default this
approach is much better than the current one.

>> As you said in the end of your post I think it is not necessary to
>> dumb any features in Typo3 but it would be an improvement if there
>> were smarter ways to hide them.
>
> yeah..

We already had a discussion about this and AFAIR the solution was to have
some extensions that will enable/disable the stuff for the different target
groups.
The default would be the "dumbed down" view, while the extensions would
offer things like:
Advanced editor view
DAM editor view
Average admin view
Power user view
etc.

This would be a real improvement.

So if we replace "remove" with "hide" in all the posts containing complaints
about something that is "too much" in TYPO3, I fully agree.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
openBC/Xing: http://www.cybercraft.de
T3 cookbook: http://www.typo3experts.com