[TYPO3-ect] T3N Article

[Patrick Rodacker]

JoH wrote on 17.01.2006 15:17:
>> Hm. For the out-of-the-box line my vision is, that the beginner has
>> not to do with TS at all. He should only have to select a skin he
>> likes. Then there should be a form to upload a logo, editing some
>> values like name, url, etc. That is the reason why it should be based
>> on well done and flexible to configure TS.
> 
> Full ACK

I see the point of using well done and flexible to configure TS but let
me explain some issues why I think the packages need support of external
HTML templates for layout purposes:

1. Beginners who are not firm with TS maybe want to use the package with
a layout which is not available through customisation or skins. They
have to dig into TS before getting the results (layout) they want.

2. Users who choose a package for a basis to develop a larger project
and who want to use templaVoila still can use the packages because the
needed extension / functionality is fully supported.

3. Users who want to contribute to this team and want to provide skins
for the packages could do this without knowing TS.




>> As skins are done by designers it may indeed be a good idea to use
>> templats for this. But skin installation should be possible by simple
>> installation of an extension. Just like the BE-Skins. It should work
>> without additional configuration with TV. Markers could be a
>> solution. The template auto-parser may be the best solution for this.
>> What do you think?
> 
> Nope! - Just HTML with markers as described in the Tutorial with the most
> misleading title "Golive Tutorial".
> This way we can follow the KISS principle and introduce the new user to
> basic TYPO3 templating techniques.

Hehe, I never had a look into that special document because of the name
at the beginning of my TYPO3 experience. Well now I don't need itAnyway,
I think to keep it simple the basic templating techniques are a good
start, but I also see the need for support of the other techniques as well.


>> A repository of TS building blocks is a second matter. I only have a
>> vague vision. The full concept will to be developed by the
>> responsible team.
> 
> As far as I understood your approach you want to define something like
> 
> lib.3LevelVerticalTextMenu = COA
> lib.3LevelVerticalTextMenu {
>     wrap = <div class="3LevelVerticalTextMenu">|</div>
>     10 = HMENU
>     10 {
>         blah
>     }
> }
> that can be reused wherever necessary. Same thing for other useful stuff.

Exactly! And the configuration should provide some settings to choose
between different menus for headermenu, mainmenu, any other additional
menu ...


> Since there are already some people (including myself) that volunteered for
> a TypoScript snippet archive, maybe this should be coordinated with this
> team.

Definitely.

Regards
Patrick