[TYPO3-ect] T3N Article

[JoH]

>> 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.

>> 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.

The designers don't have to wait, since they just deliver the design that
will be converted into a TypoScript-powered extension.
And: Yes, we definitely need another TS-Setup for each design/layout since a
blog will need another setup than a shop.

I guess you mean something else, which is more related to the Zen-Garden
concept.
Different looks for the same design. Just another fancy plastic cap for the
same mobile phone.

In this scenario it's just vice versa: The coders will deliver the HTML
output and hand it over to the Designers, that are not allowed to modify the
code itself.

>> I think more "proof of concept" is not necessary.
>
> Remember, I am speaking of the out-of-the box packages, not of the
> snippet collection. Proof of concept is done for me, when you can
> download the first TYPO3 Blog package from here
>
> http://typo3.org/download
>
> and if you can exchange the FE skin by installing a new extension
> from TER.

In fact you would not install or extend anything with this "extension".
Its just a bunch of CSS files with corresponding graphics that has to be
downloaded and then activated by "installing" it.
It will override previously installed designs for the same package then.

Technically this doesn't seem to be a big deal. It's all about sophisticated
styles - nothing more, nothing less.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
http://www.cybercraft.de