[TYPO3] No tutorials? Draft idea attached...

[Dmitry Dulepov]

Hi!

dave ashton wrote:
> Look at the joomla site for what it has been used for...very big sites, so
> joomla is enterprise level.

Just using something for big sites does not make system enterprise 
level. It is more about its organization, architecture, features, etc.

> Do you think future developers will jump on board with using typo3 and
> dismiss other CMS's if they knew the amount of learning involved, etc?

May be. If they have reasons.

> Are you saying you cannot develop an enterprise level site with others and
> thus typo3 is the only enterprise level open source solution so just get on
> with the learning curve no matter how long it takes?

I did not say that.

> Basically, i'm saying, if you have not used a CMS before, which would you
> chose if you knew all the options - learning curve, functionality, community
> size, clear documentation, etc.?

I chose typo3 after studying and comparing of several CMSes (including 
mambo). It best suited my needs and I never regretted my choice.

> Would you want the situation in a few years where, typo3 developers have
> started using other CMS's as typo3 has too much of a reputation of being too
> hard to learn.

I do not think so. For serious application they key is not learning 
curve but features and possibilities.

> I think this is unlikely, but I read too many posts on the net to say, typo3
> is really hard to learn and it seems this is only true with typo3.

Well, I never managed to learn how to manage mambo-driven sites :)

> All this is academic.........the typo3 developers seem to be making the
> solution easier to learn with templavoila, etc. and they have their own
> methods and ideas of implementation. All a continuous process and like all
> humans, some we get wrong.

Yes. This is why feedback from non-developers is so important and why I 
asked Matthew for comments about TV in another branch of this thread. We 
(developers) must develop typo3 further but we must not forget about 
people who use the system. System should be a reasonable compromise 
between functionality and usability for average user. If feature is too 
difficult, it may be unused but most of people even if it is great, 
spectacular, etc. We need (and we try) to listen to opinions and make 
typo3 more "available". However we cannot go to far or system will start 
to degrade.

TemplaVoila in my opinion is a good compromise between power and 
simplicity. It make take time for administrator to map all objects. But 
it is much simpler for ordinary user if he needs to select different 
layout for one or more pages: just two clicks in page properties to 
select new template.

> Like I said, typo3 i think is the best open source solution I've come
> across, just wish it was clearer to understand with more English resources
> and tips, that's all!!!

I completely agree! Unfortunately there is no appointed contact from 
develper's to documentation team. This is a mistake. There should be one 
whom documentation team may bomb with questions, suggestions and 
complains. If contact between core and documentation team improves, we 
could get much more and better documentation.

-- 
Dmitry Dulepov

Web: http://typo3bloke.net/
Skype: callto:liels_bugs

"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)