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 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
>  
I usually do that as a matter of course ­ one global style sheet that I
usually call Œdefault.css¹, which sets up all the default styles (no
kidding?), and then a page- or section-specific style sheet to deal with
the, well, specifics (man, I think I see a pattern here...). I find that it
makes managing larger sites much easier.

-- 
Kevin Futter
Webmaster, St. Bernard's College
http://www.sbc.melb.catholic.edu.au/


#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared 
by MailMarshal
#####################################################################################

This e-mail and any attachments may be confidential. You must not disclose or 
use the information in this e-mail if you are not the intended recipient. If 
you have received this e-mail in error, please notify us immediately and delete 
the e-mail and all copies. The College does not guarantee that this e-mail is 
virus or error free.  The attached files are provided and may only be used on 
the basis that the user assumes all responsibility for any loss, damage or 
consequence resulting directly or indirectly from the use of the attached 
files, whether caused by the negligence of the sender or not. The content and 
opinions in this e-mail are not necessarily those of the College.


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

Reply via email to