I worked up something for 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 departments will want to release unique controls and content
elements that won't be able to pick up the existing styles. This will
relieve pressure on the framework CSS files.

I'd suggest that CSS be added to a project and validated before going
out, and use ID to isolate areas where you can. You should be able to
clean out the content.css and controls.css files periodically.

The multiple stylesheets are a concern, but your base framework can be
combined and compressed and served from somewhere else as others have

You can do much the same for the javascript too.


Paul Minty Director

mintleaf studio 
We design & create stylish websites

Post: Box 6 108 Flinders Street Melbourne VIC 3000
Level 2 108 Flinders Street Melbourne
T. 03 9662 9344   
F. 03 9662 9255   
M. 0418 307 475



> -----Original Message-----
> [mailto:[EMAIL PROTECTED] On Behalf Of Jens-Uwe Korff
> Sent: Thursday, 24 April 2008 4:31 PM
> To:
> Subject: [WSG] An efficient CSS architecture
> Importance: Low
> Hi all,
> I'm currently in the lucky position to be able to design a 
> CSS architecture from scratch. I was thinking of creating a 
> layered approach where I have a CSS layer for
> - the CSS reset
> - the site layout (structural parts, ie. columns, rows, 
> header, footer)
> - the site's elements (boxes which can be reused across 
> pages; a box might contain images, heading, paragraphs)
> - the site's skin (colours, sprites etc.)
> I'd like to know if you have been through this thought 
> process and if you have proven concepts that you would like to share.
> (You can email me offline too, but we've got a long weekend 
> here so I'll contact you Monday.)
> Thank you!
> Cheers,
> Jens 
> The information contained in this e-mail message and any 
> accompanying files is or may be confidential. If you are not 
> the intended recipient, any use, dissemination, reliance, 
> forwarding, printing or copying of this e-mail or any 
> attached files is unauthorised. This e-mail is subject to 
> copyright. No part of it should be reproduced, adapted or 
> communicated without the written consent of the copyright 
> owner. If you have received this e-mail in error please 
> advise the sender immediately by return e-mail or telephone 
> and delete all copies. Fairfax does not guarantee the 
> accuracy or completeness of any information contained in this 
> e-mail or attached files. Internet communications are not 
> secure, therefore Fairfax does not accept legal 
> responsibility for the contents of this message or attached files.
> *******************************************************************
> List Guidelines:
> Unsubscribe:
> *******************************************************************

List Guidelines:

Reply via email to