Many doubts about Typo3 template system -

i new in typo3 (i came joomla , wordpress) , finding many difficulties understand how template handled in typo3 (it seems me here situation more complex in joomla , in wordpress).

i have installed , testing version of typo3 introductionpackage-6.1.3.zip

in joomla , in wordpress template html structure (which marked in various areas of page cms modules placed) , related css settings.

in typo3 seems me situation different or wrong?

at moment reading section of official documentation makes reference default template of typo3 introduction package: http://docs.typo3.org/typo3cms/gettingstartedtutorial/templates/index.html

it pretty clear me difference between static content , dynamic content of website created using cms (this not different others cms joomla or wp)

dynamic content: dynamically created cms (executing queries) menu (it db table menu voices , script renders menu on page)

static content: somethin fixed title of website or background immage

ok, untill think pretty clear me have many doubts when documentation speack template record way implement previous principle.

here: http://docs.typo3.org/typo3cms/gettingstartedtutorial/templates/%28%28generated%29%29/index.html

it that:

this control element instructs typo3 how handle branch of page tree.

in particular immage show how modify these template record introduction package template (introduction package name of template provided package or what?):

then on section on documentation say:

if edit template "introduction package" see fields empty. each website need typoscript template on root level, in case "introduction package" template. typoscript configuration of website can quite long therefore possible make many small typoscript templates included in main template. better maintenance, typoscript of introduction package has been put folder 'typoscript templates'. thing "introduction package" template include "root" template in turn includes other templates.

and totaly obscure me: have understand typoscript configuration language can used configure frontend (so think can use configure how page appear) can't understand following assertions:

1. what mean that: for each website need typoscript template on root level, in case "introduction package" template ? have installed typo3 introduction package , have web site !!! root level of website? welcome typo3 node in list section tree? in pracatice assigning specific template root of website , used in subnodes (all pages home, typo3, features, etcetc)?

2. what mean when say: for better maintenance, typoscript of introduction package has been put folder 'typoscript templates'. folder? have not

3. what mean when say: the thing "introduction package" template include "root" template in turn includes other templates.?

tnx much

andrea

the root level of website page called home. has globe instead of normal page icon, because flag use root page set in page properties under behavior.

when access page in typo3 cms, walk rootline until finds root page template record. in case, indeed record called introduction package, more important, record of type template.

ok, far have found template request. typoscript comes play. on normal request, template engine search object named page (usually) of type page. simple template is:

page = page page.10 = text page.10.value = <h1>hello world</h1> 

which prints hello world on website.

what happens next depends on template approach chosen (marker base, automaketemple+marker, templavoila, fluid, fedext, ...). means typo3 cms not have 1 template approach (or 1 kind of template), extensible , flexible, can combine them.

in introduction package uses automaketemplate+markers approach. includes ready html template, automatically creates blocks based on rules , replaces blocks dynamic content.

ok, find configuration this? actual template file fileadmin/default/templates/introduction_package_site_structure_template.html. typoscript configuration in fileadmin/default/typoscript. there can find file called setup.ts. includes other typoscript files. there various folders, e.g. menu menu definition, block dynamic blocks, etc. configuration of automaeketemplate in extension/automaketemplate/setup.ts.

the sections defined of automaketemplate replaced in page/setup.ts.

the full typoscript defines tree structure of objects configuration. can view full parsed template either template analyzer or typoscript object browser find in template tools in dropdown select box on top of module.

the separation of typoscript several files done purpose of configuration inside files. meant easy maintenance , not easy learning. can use template analyzer see full template generated out of fragments , ts object browser see kind of configuration tree results in.

this might sound bit difficult @ first, compared primitive template systems of other products, gives great possibilities yet easy maintain, if major updates.