[TYPO3] No tutorials?

[Ron Hall]

Earlier it was written:

>> 
>> At least here in Germany TYPO3 is on it's way to become this market leader
>> even though most of the documentation is written in english and thus even
>> less understandable than for a native speaker.
>> A few years ago we had to explain our clients that there is a CMS called
>> TYPO3 and what it could do for them - nowadays they are asking for it,
>> because they know it's one of the best and they just want to have it.
>> 
>> So the question still remains: What is the big difference between german
>> developers and implementors and for example their american equivalents?
> 

I will try to give my perspective on the difference between the TYPO3
community in Germany compared to the U.S. and give an additional quick
thought on the original subject of documentation.

First, I live in Dallas, Texas and have had some contact with TYPO3 since
version 3.6. I put up my fist live site (800 pages) this year for my
employer and they have joined the TYPO3 association. I have also had the
pleasure of meeting Kasper twice in the last two years here in the U.S. I am
a great believer in TYPO3 but am not blind to its particular challenges. I
am such a proponent of the system that I intend to base a freelance business
on TYPO3 development.

For some time I have thought about the difference in the TYPO3
situation in the U.S. compared to Europe. Frankly, I am sometimes jealous of
my German peers because I wish we had the same situation here. Someday maybe
we will but not yet.

TYPO3 is based on the idea of sharing. Each of us sharing our code, our
time, our struggles so that others can be helped in their TYPO3 journey and
who then can return the favor and help us by sharing their own code and
ideas. This process however is impeded by distance. Now, it is true that the
nature of the internet helps mitigate the effects of time and distance but
it does not eliminate them.

What am I getting at? The growth and vibrancy of the European TYPO3
community is greatly enhanced by the by the ability to connect personally
beyond the computer screen. This is why events like the Snowboard tour and
availability of so many local German Users groups are so important. Learning
TYPO3 is so much easier when you have someone you know personally that is
traveling the same road.

Though I know I would be welcome, an event like the snowboard tour seems far
removed for me and is much more difficult for me to consider attending than
for someone in Germany or France. I am happy my European friends have that
opportunity. I believe it and other such events and particularly the
connections they foster is why TYPO3 has such a solid footing in that area.
We do not have the same opportunities in the U.S.

When I first found TYPO3 I was intrigued by by its power and flexibility
(still am). But it was no secret that I would have to make a major time
commitment to learn it properly. I decided to make that commitment because I
believed the effort would pay off (and it has). However, at the time, I did
not have nearly as many CMS's shouting "try me" as the newbie has today.
It helps today's new user to stay with TYPO3's learning curve if
he personally knows a TYPO3 veteran that will assure him, " Go for it, you
will not regret the time spent learning. It will pay off big down the road."

Personally, I have taken steps (though small) to help with this. We have
established a Typo3 Users Group in the Dallas area. We have met three times
already and it has been great for all of us. I will be officially announcing
the group to the mailing list in the next few days, but if you live in our
area you can get details at www.typo3dallas.org.

Bottom line, TYPO3 can be learned on your own (I have done it) but personal,
beyond-the-computer-screen connections make a huge difference in the
experience.

This brings me to my documentation comments. First, some of our
"competition" may seem at times to have better documentation but that may be
because they have fewer and more restrictive features AND they have not been
around long enough for their documentation to become dated. Remember in the
midst of challenges that you are working with mature (and maturing project)
with a substantial history and that is a good thing.

Having said that, it is still very important to have up-to-date documents,
especially the introductory documents. If a developer experiences early
progress with TYPO3 they are much more likely invest in the learning needed
to use its great power. Those who experience confusion early on will not
develop the confidence that the effort will be worth the reward and will
search for other solutions. TYPO3 is not for everyone but it is a shame to
loose people who could have fallen in love with TYPO3 because of bad first
impressions. Remember, most folks' initial interaction with TYPO3 is through
the introductory documents and not through personal contact with established
users in TYPO3 community (who are wonderful people).

Thanks for putting up with my ramblings.
Ron Hall