the odd
> occasion where something gets by. (9 times out of 10that is because I have
> missed a dependant file!)
>
> Mike
>
> -Original Message-
> From: [EMAIL PROTECTED] on behalf of Jens-Uwe Korff
> Sent: Mon 28/04/2008 08:27
> To: wsg@webstandardsgroup.org
>
: wsg@webstandardsgroup.org
Subject: RE: [WSG] An efficient CSS architecture
I am currently looking into CSS compression. This has, however, the
disadvantage of removing effective live debugging with Firebug because
all CSS rules will be on one single line. How do you address this
pr
Hi Paul,
thanks for your thoughts. Could you share why you went for Yahoo YUI
rather than e.g. Blueprint CSS?
Please explain to me what you mean with CSS for a "creative workgroup"
and "dev workgroup". Why is this distinction necessary?
I am currently looking into CSS compression. This has, howe
Jens,
I worked up something for www.iasbet.com which was reasonably robust.
This was before we adopted the Yahoo YUI for our in-house development.
I'd suggest you create separate CSS files and workflows for a creative
workgroup and a development workgroup (content.css and controls.css) as
both de
ruft.
Ted
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Karl Lurman
Sent: Thursday, April 24, 2008 8:42 AM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] An efficient CSS architecture
Jens,
I recommend googling CSS Frameworks.
Also, I recommend looking a
Jens,
I recommend googling CSS Frameworks.
Also, I recommend looking at a site I implemented a CSS framework of
my own. It sounds very very much like your approach.
http://www.athletics.com.au
It works on the concept of layers that can be used to progressively
enhance the visual appearance of a
