I also have a habit of giving my CSS files (and JS, SWF etc) a name of xxx_v1.css. That way, if you make an update, you can upload a new version (xxx_v2.css) knowing that the old one won’t be cached.

@martin Another advantage is using the same ID and class names over and over again.

@jamie I usually start with a basic template folder too, which saves so much time in the beginning.

@anna I will certainly give that post a read.

She uses the term “pattern portfolio” instead of kitchen sink, but the idea is the same, as you put “because even if you don’t include a table, or list at the moment, you (or your client via WYSIWYG) may do in the future.”

She stresses the importance of defining and ordering the CSS as components rather than specific page styles, and at the bottom of the stylesheet, having overrides for the general styles.

I tend to keep as much as I can in one stylesheet, and just have separate ones for IE and print styles, but it depends very much on the site. For a very large site, or one with more than one person editing the CSS, I might choose to split it up. I did this for Scrunchup, so the issue specific colours are in one stylesheet, and the layout is in another, just so things are less likely to go wrong if someone edits the wrong bit.

nice post, i use a default stylesheet based on the one distributed with CSS mastery, i have not really updated it for a while but it does the job. Depending on what sort of project i am working on, i have a few “quick start” Zips / Scripts set up. A double click gives me the starting files / folders for what i need, i just either copy it to where i need it, or put the right directories into the script.

Nice post, nice redesign too

Jamie & Lion

However, I know I could save a shed-load of work by employing the DRY philosophy ad setting up HTML/CSS templates.