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

Tyler Kraft headhunterxiii at yahoo.ca
Fri Oct 6 11:01:54 CEST 2006


Actually I don't think it is possible to get typo3 powerful and complex 
and easy to learn. I understand very well the way a car works, but thats 
probably because I have been tinkering with them for years and I have a 
mechanical engineering degree.... But I would struggle to sit down and 
build one! The point being that with a lot of effort and hard work and 
experience someone can understand how something works, but it takes much 
beyond that to create the item (or in this case create with the item). 
Meanwhile just about anyone can be taught how to use the item (drive a 
car or edit content with a cms)

So I think if we want to make it easier to learn we need to start to 
realise that there are different needs within the CMS, and also 
therefore different documentation needed depending on the need of the 
CMS. So if all the documentation is written from the perspective of the 
high end user or developer (often also one and the same) then that 
doesn't mean the current documentation is at fault, it means that it 
doesn't serve that particular segment of the market/user.

So I'm not defending the documentation as it currently stands... at 
least in my own personal opinion I'm just tired of people whining and 
complaining about how hard it is and how the documentation is so bad! 
How often do we see someone say "The documentation on XXX is so bad that 
here I've written this" - Never!

If the documentation is hard to understand for a newbie then why don't 
some of them write documentation that does suit their needs instead of 
expecting others to do it?



Peter Kindström wrote:
> 
> Hi!
>> Maybe, I'm missing the point - if you want typo3's power and flexibility,
>> you have to just get on with the learning curve. It will get better, but
>> it’s a slow process.
> 
> But... is it really not possible to get Typo3 powerful, complex AND easy 
> to learn? Couldn´t that be one of our goals? Instead of just "ignoring" 
> the problems and defending todays documentation and learning curve.
> 
> I want to improve TYPO3, not conserve it!
> 
> 



More information about the TYPO3-english mailing list