Have a look at the Adobe.com website, see what they are doing (talking
about massive).
I also tend to divide layout/fonts/colours into separate files.
You could then have different colour templates, font templates (where
font sizes change for example), etc.
As css files can become big, I think
On 13/3/07 3:01 PM, Cole Kuryakin [EMAIL PROTECTED] wrote:
Hello All
I¹ve got a site that has a fairly MASSIVE style sheet. It¹s quite long as the
design spec dictates a number of different pages be layed-out differently.
Accordingly, its becoming quite tedious to find certain style
One of the best things we did was to follow Doug Bowmans (webstock '06)
suggestion to break up stylesheets into logical components and include them in
one main file.
Our 'styles.css' file now looks like this:
-
@import url(styles-contentTables.css);
@import
not seeing.
Care to enlighten?
From: Paul Bennett [EMAIL PROTECTED]
Subject: RE: [WSG] Global and page-specific style sheets
One of the best things we did was to follow Doug Bowmans (webstock '06)
suggestion to break up stylesheets into logical components and include them in
one main file.
Our
Hi Chris,
Basically if I'm looking to change something in the main nav, I look in
mainnav.css, if I'm altering a header for a table in our content area, I look
in contentTables.css etc, etc.
The main file was 30K (!) before we started trimming it down and breaking up.
Yes it's more http
Basically if I'm looking to change something in the main nav, I look in
mainnav.css, if I'm altering a header for a table in our content area, I
look in contentTables.css etc, etc.
Or if you've got Firebug, right-click on an element, 'Inspect element' and
it tells you exactly what line
I don't have a problem with it, in fact the site I'm working on at the
moment has 30 separate style sheets. However, remember that every style
sheet will be a separate HTTP connection to retrieve it, so no matter how
fast someone's connection is, they still have to make multiple HTTP requests
to