Hi Christoph, Philipp and others,
As someone who actually helped creating the introduction package and working
especially on the Typoscript part, I'd really like to second Philipp's answer.
I did not 'invent' that structure (it was proposed by Patrick Broens) and at
first I also thought it was well-created but overkill, now I can no longer live
without it. The main reason is that once you really understand the structure,
everything has a clear place and is placed in the correct order, and you never
have to search long to find what you're looking for. This is especially useful
when you're working with more people on a project, but it's also very helpful
when you have to fix something in a site you made 3 years ago....
I use a very similar structure, but then in files instead of database records.
The good thing there with having many separate files is that you'll have less
merge conflicts while working with more people.
So, even for my small one-man-show projects I use this structure nowadays.
Some documentation of how and why would certainly be great.
Cheers,
Loek
On 02-07-12 21:55, Philipp Gampe wrote:
Hi Christoph,
Christoph Stadler wrote:
WHat i'm wondering/missing is if the way the Introduction Package is
built somehow represents a 'best practice' approach ? Especially the
extreme segmentation of the templates and scripts into folders,
subfolders and then again in the filesystem makes me wonder ... what was
the concept behind this ? Is this just taken to the extreme for demo
purposes or is this how it should be done in the eyes of the typo3
developpers ?
Yes, this was build at T3UXW09 with best practices in mind.
The structure look wired at first, but follow some deep logic.
Actually if you are new to a project, it helps to find stuff, because
everything is stored in a certain order.
For a small project, this is overkill.
For a large project, you better store your TS inside files and include
those, because then you can version them.
It is actually good practice to follow this approach because most likely
your project will grow and you will loose the overview over where certain TS
comes from.
Another - quite similar - approach is it to store TS in parts for each
marker you replace, all on one folder.
Both approaches have in common that you can easily port whole TS trees from
one site to another via the import/export feature of TYPO3.
Cheers
_______________________________________________
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
