[TYPO3] Complicated documentation? No reference guide? Do you know any good documentation?

[Cate & Peter]

Hi Karol

> > I'm wondering, if you agree with me, that almost all of the
documentation to
> > TYPO3 is really non-intuitive.

The story is documentation is an old one. There are a couple of reasons -
first, the people who wrote it are predominantly coders, and people who have
a good understanding of basic concepts, and maybe have forgotten how much
they know intuitively that the rest of us don't :). The second is that
coders like coding, not writing manuals (overgeneralisation I know). The
third is that coders are always busy improving their coding projects and
debugging, and documentation is put off. I find that the WEC documentation
is always excellent, so for things like tt_news, and basic extensions that
the WEC team have put together in their package, they usually have some
help.

TSRef is handy ... but only if you have a starting point, when you are
learning. I usually try to find some code that nearly does what I want, and
look to see how to tweak it.

And Christopher, regarding your article...

> For this reason, I wrote the following article about using the
> TSref--have a look and if you (or other readers of this thread) have any
> suggestions for additions or  changes, please let me know:

I had a look at it ... but honestly, for me, it went straight over the top.
All the jargon that I don't understand in the TSRef is all there in the
article, and so I still don't understand it. I think maybe you are a 4th
year apprentice and ready to become a tradesman, while I still have to pass
my entrance exams :)

That is why I made my own blog at typo3newbie.com, so that I can paste
snippets of information I find out that makes everything else clearer for
me. It is like a little "hint book" that I keep online. (I am amazed the
number of times I search for something on Google, and my own site comes up
with a hint :))


Cate Deans Smith