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

[dave ashton]

Hi all,
I wrote a few listings on being frustrated with documentation, etc. a few
months back.
I even looked into using joomla, as typo3 problems were just taking ages.
Joomla still using tables as the base layout!

I've obviously stuck with typo3 as I've got over the 'wall' if you will. I
have a set method to get a basic site up (made my own cheat sheet) and
running and go into the object browser to change a few things around for
extensions (after going through tsref loads of times!)

It has taken 1 1/2 years to get to this point.
I understand with loads of power comes a high learning curve. However, as
with others, I felt this was to do with documentation, not realizing
typoscript (notice 'script' in the word, i.e. scripting!!!!...ahem!) had to
be learnt aswell (lots of time needed!) Also, depending on how your setup,
config., extensions have been put together depends on how other aspects of
your install will work. (ooohhh, lots and lots of options which at first
looks like an alien language!!!)

Thus, I have one method of installing, etc. as I learnt this way. I don't
use other methods like templavoila (yet!). I use the same plugins for each
site for a base install. Anything I can't make extension-wise, I get another
company to build for me.

So, why have 3 or four ways to do the same job?? Is one better than another?
Will in the future, typo3 developers split into factions who believe one way
is better than another and end up developing their own CMS with their own
way of doing things? Will people spend all their time learning all the
different methods and not getting anything done? Will we all just become
plumbers, as a pipe is a pipe?!!?

Lots of options is great, but when each option can take months to learn and
implement, especially for a beginner (..and is this way of learning the best
route??)
I learnt to use 'css styled content' , 'template auto parser' and 'html/css
styling' then import a dummy page tree, then style up the marker divs. Is
this the best or most efficient way? I don't know!

Therefore, I think there should be one method for all functionality, i.e.
Templavoila for templating, indexed search for all searches, etc. Extension
developers can then develop off these extensions for their own
functionality.
Future extensions with specific functionality from the originals, will
hopefully, be easier to understand and have the same common feature to
edit........or am I just talking bolloxs as usual.

At the end of the day, we're all web designers/ developers with different
degrees of knowledge and experience with typo3 and I think the bottom line
for all is to complete a job on time and deliver a good system, without
spending all day and night for months working on things that seem like they
should take a quarter of the time.

I think, although typo3 has been going for a few years, its early days,
still. Hopefully, in a few years there will be standard ways of implementing
functionality, step-by-step documentation (put this here, change that there
- don't assume too much prior knowledge, which all developers do....(talking
to client "edit the config. Area"...client-"whats that, where does it
live"??!!??!)

I think I saw recently, joomla being up for a CMS award with Drupal,
etc....Eh!!, How did they get there when typo3 is clearly better?
Simple, a web designer can learn joomla quicker and easier, more docs. and a
bigger community. It may not do what typo3 can do, but does the client know
that?  ....no. If it takes from no knowledge to 1 week to get a basic site
running in joomla and 1 month with typo3, what would you choose? (yes, I
know you should look into what both can do power-wise, but on the surface of
looking at both joomla and typo3 developer sites, they look like they can do
the same thing. Only with going down the road of developing in both can a
true comparison be made.)

No CMS is perfect and being open source, all have to chip in, I just wish it
was just easier to bloody learn!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Last rant - I wish there were more English typo3 books, wish there were more
English typo3 books, wish there were more English typo3 books, wish there
were more English typo3 books........................!

Dave



-----Original Message-----
From: Matthew Manderson [mailto:matthew at manderson.co.uk] 
Sent: 05 October 2006 10:00
To: typo3-english at lists.netfielders.de
Subject: Re: [TYPO3] No tutorials? Draft idea attached...

Hey Dmitry!

> Looks like it uses MTB. I afraid new users may learn much faster if they
> use templavoila's ppint-and-click templating than writing markers here
> and there... Did not read further since I do not use MTB for ages.

So I chose ###markers### does it matter? Let's not start another TV vs
subpart markers discussion. I recall it was concluded the some people
prefer either and yes TV does solve some complex problems ordinary
###markers### would find tricky.

I have used templavoila now for my last 3 sites because I wanted to learn
that way.

I don't have a considered view between either templavoila or subpart markers
yet I do think templavoila adds greater BE confusion for absolute
beginners. In another thread another day I'll work through those points
more fully.

The simple reason I chose to pursue the subpart markers route is I think,
closest to the historic TYPO3 docs way of doing things.

The newbie workload difference between adding a few ###markers### in an html
file, or going through the TV process of installing two extensions, one BE
refresh, and clicking around the templavoila BE modules that are not
mentioned in any of the core TYPO3 docs and figuring out whether my mapped
object should be an Element or a TypoScript Object Path - well for me
looking at newbies, ###markers### are the easiest route.

This doc is not for you Dmitry so put it down and don't read it again...

Enjoy!
Matthew

  

_______________________________________________
TYPO3-english mailing list
TYPO3-english at lists.netfielders.de
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english