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 download all the documents, thus slowing down the site. Once the style
sheets are cached then this delay will be reduced.

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Cole Kuryakin
Sent: Tuesday, 13 March 2007 3:01 PM
To: [email protected]
Subject: [WSG] Global and page-specific style sheets

 

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 blocks that
need to be altered/tweaked as development continues.

 

So, I'm beginning to think that the better way to accomplish this is to
attach a "global" sheet in the head that would take care of all "generic"
issues and page requirements.

 

Then, in those pages that need "special handling" I would attached separate
sheets that would address page-specific requirements.

 

BTW: This site is a dynamic one (php) so these special-case pages are
"included" depending on query-string variables/conditions.

 

What do the good folks say here about this particular topic? Is this a
normal (and preferred) workflow when one has to deal with long and unwieldy
style sheets?

 

Are there any "best practice" guidelines for such an issue?

 

Cole

 

 

 


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to