[TYPO3-ect] T3N Article

Patrick Rodacker patrick.rodacker at the-reflection.de
Wed Jan 18 21:09:00 CET 2006


JoH wrote on 18.01.2006 00:28:
>>> 1. Only clean and valid Code
>> +1
>>
>>> 2. Almost accessible layout
>> 99%
>>
>>> 3. Should display the same in common browser/system environments
>> +1
>>
>>> 4. Separate style sheets for different areas (common, topmenu,
>>> leftmenu, content, whatever)
>> ???
> 
> This is necessary to keep the different CSS files small and accessible.
> If you are using one big CSS file it's almost impossible for someone who
> didn't create it to find things he wants to change.

Good point. Should be communicated within the CRG as well and should be
stated in a document about the general approach of creating TYPO3 packages.


>>> They can also include some dummy content we can replace during
>>> "TypoScripting" just to give us a preview of the look and feel.
>>> No markers or subparts necessary since this will be done by the
>>> TS-Crew.
>> Do you really want to make a special TS for every design? The
>> designer would have to wait. Waiting brakes motivation. That can only
>> be a solution for very special situations.
>>
>> Think KISS. I guess there are at least 2 ways to make it still more
>> simple.
> 
> We are still not talking about the same things here.
> When I say "design" it means a complete HTML/CSS template.
> Different layout, different menus, differen content and so on.
> The design of a blog page is something else than the design of a shop
> system.

I think we should officially define the terms 'design' and 'layout' for
better understanding. At least within this group. E.g. I am used to use
the terms in the other way round then you, maybe others do use only one
term at all. In my opinion the problem is, that both terms are valid to
describe a structure as well as the visual representation of something.
Maybe a clearing statement would be useful.

Using your definitions I think a shop package should provide one
standard design, but offer the change to a new design in an easy way.
Providing markers for an external HTML file and a simple configuration
of menu types, content output (columns), etc. should do the job of
providing full control about the design / layout of the package. One of
the strengths of TYPO3 is the support of every possible layout / design.
Imho this support should not be limited to provided 'skins' or
complicated TS configuration within any of the packages


With best regards
Patrick



More information about the TYPO3-team-extension-coordination mailing list