[TYPO3-dev] Developing Standards - CSS

[Christopher Torgalson]

Hello,

2010/2/10 Erik Svendsen <erik at linnearad.no>:

> Personaly I more and less turn of every bit of CSS from extensions, change
> stdWrap and HTML-templates to suit the design of the site. The result is one
> CSS (maybe two) CSS-files, and they are mostly small.
>
> And to Tomas, CSS-styling takes time in commercial CMS to, many of them have
> more CSS than a typical TYPO3 installation. Neither are the html in any way
> pretty to. I have counted up to 15 nested divs in installations with
> commercial systems and nearly 100 kB with CSS.


Indeed. This is one of the places where TYPO3's current methods are
radically better than e.g. Drupal's. In Drupal, many modules provide
their own CSS files–and though these can be overriden, they can not be
simply turned off. This results in Drupal having an absurd problem
where it's possible to run afoul of a technical limitation of Internet
Explorer where "only" 31 stylesheets can be included in the page head
(!)

My opinion in general is: don't force the use of ANY markup or css
(i.e. make it possible to modify *every* bit of HTML, and make sure to
provide the CSS in a way that can be turned off), and provide stdWrap
on everything (just as Jigal suggests above).


-- 
Christopher Torgalson
http://www.typo3apprentice.com/