Hi Ian, Here is one approach to take. I have used this basically when i have different "skins" for the same template, where just the color changes and the structure remains the same.
usually the whole HTML structure is encased by one single div, that usually does not have a style associated, unless in want make something that changes the design overall: <div id="frontend">......</div> Would i like to add a blue skin, i would simply add <div id="frontend" class="blue">......</div> and can so subsequently change the styles that i require to give the site a blue look and can leave anything else as is. Our projects structure just uses different stylesheets when need to make adjustments to IE Versions with Conditionals. Otherwise its just one stylesheet containing comments that markout the sections. Usually Standard styles that describe basic html attributes com first: html, body, img, form, td and so forth... Then sections get added that describe the content area in more detail and after that styles for the footer area. Should there be changes due to skins or special pages that fallout of the standard layout, these follow as their own sections in the specific content area. You can see a more complex example here. It does not use skins in the sense of changing the whole layout, but i think it illustrates quite well what i mean. http://www.parkettboeden.at/web/css/common.css regards, Jens On 10/9/06, Ian Piper <[EMAIL PROTECTED]> wrote: > Hi all, > > I'd appreciate your guidance on how best to organise my CSS styles. > > I am designing a site that has an overall design with some variations > on some pages. For example, I have this for a page banner style: > > #page_banner { > background: url(../images/banner_page_name.gif) no-repeat; > width: 990px; > height: 102px; > } > > where I will have a number of different banner_page_name.gif files. > > My client also wants to have colour variations within the overall > them on some pages, meaning that I will have to vary background and > keyline colours. > > The question is one of how best to organise my css files. I could > have all of the styles defined in one .css file and put the > variations in the head of each html file, or I could link to a style > sheet designed specifically for the page, and then import the more > general style sheet. From what I read it appears that linked styles > override imported styles. The latter seems a cleaner approach, but > most of the sites styles would end up in an imported style sheet, and > I understand that older browsers do not support importing. > > Anyway, I can't figure out in my own mind which is the best approach, > and can't find much on the web about it. Any guidance appreciated. > > Thanks, > > > Ian. > -- > Dr Ian M Piper > [EMAIL PROTECTED] > skype: ianmpiper > -- > Where is the wisdom we have lost in knowledge? > Where is the knowledge we have lost in information? > > > ______________________________________________________________________ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 > List wiki/FAQ -- http://css-discuss.incutio.com/ > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > -- So long and thanks for all the fish. ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
