[TYPO3-dev] Developing Standards - CSS
Erik Svendsen
erik at linnearad.no
Thu Feb 11 07:18:51 CET 2010
Jigal van Hemert skrev:
> Hi,
>
> Georg Ringer wrote:
>> Tomas Norre Mikkelsen schrieb:
>>> When i develop / setup TYPO3 websites, 30-40% of my time is for adapt
>>> css-styling, such the plugin match the generel design template.
>> I do 80% coding new extensions because I can't use existing ones
>
> This only means that extensions are not flexible regarding styling, etc.
>
> If extension programmers would stick to a few basic rules:
> - use a flexible HTML template
> - do not generate HTML in the PHP code
> - use stdWrap on every data field
> - include links to CSS and JS in the HTML template (see Dmitry's book
> for code to include those parts in the page)
>
> then you would only need to change the template of an extension (and
> possibly a bit TS to format the data) to display things exactly like you
> want them displayed.
>
> Adding the ability to create custom markers in TypoScript (quite simple
> too) would add a bit extra flexibility.
>
> Regards,
> --
> Jigal van Hemert.
Straight to the point - agree in every part.
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.
But of course we should try to help/force developers to make better
html-templates, following good practice for how to code fleksible HTML.
And some guidelines could be a helping hand. Also "sharing" better
templates could help.
Regards
Erik Svendsen
More information about the TYPO3-dev
mailing list