[TYPO3-dev] Extension Development and CSS

[Daniel Huf]

I really like the idea to define a CGL for CSS and HTML.
But maybe we should define a kind of canvas we could use.

Why not try to stick to the standards, even to be able to validate our 
code with it.

For example let's say we try to stick to XHTML STRICT [1] with WCAG [2] 
so we could validate our extension code with a tool [3] while developing.

If we follow all these rules, we could even enforce the SEO and 
accessibility of TYPO3.

[1] http://www.w3.org/standards/techs/html#w3c_all
[2] http://www.w3.org/WAI/intro/wcag
[3] http://www.totalvalidator.com/

Dmitry Dulepov wrote:
> Hi!
> 
> On 2010-02-10 14:53:52 +0200, Tomas Norre Mikkelsen said:
>> When i develop / setup TYPO3 websites, 30-40% of my time is for adapt
>> css-styling, such the plugin match the generel design template.
>>
>> Is it possible to agre that developers has x number of predefened
>> html-tags to use, such if you have a standard installation you will be
>> able to install and use a plugin must faster.
>>
>> I know you can start stripping all plugin-internal css but if the was
>> made an agreement on you should use eg. following tags with out any
>> styling or classes. just plan html-tags.
>>
>> h1, h2, h3, h4, h5, h6, a, an so on..
>>
>> With this ajustments you will have a CMS that acts more like
>> commercial CMS systems, but still have the open source flexibility.
>>
>> Follow my idea ? Or am i complete misunderstod something ?? :)
> 
> I usually use header starting from H3 (my idea is that H1 & H2 is for 
> upper–level content). Next all semantic markup such as <p> for texts, 
> <ul> or <ol> for lists, <span> for logically stylable pieces, etc.
> 
> There are certain problems with various CSS designers. They often set 
> styles globally for, for example "#content ol", so extension's default 
> styling simply does not work. For example, one my extension had to show 
> ordered information in two columns. I did it with <ol> but all styling 
> was completely broken by the global CSS markup, which overwrote my 
> styles. We had a hot talk with the designer and ended up on giving an 
> "id" to the <ol> and styling it specially.
> 
> So it is not only about extensions :) Certain requirements exist for 
> upper–level designers too.
>