Like many of the other commenters, I break the code into reset, global elements, layout, modules/blocks, and then special overrides if any.
I'll admit it's a personal preference, but as a team consideration I don't recommend the 'all properties on one line' approach. It's discouraged in other languages so why do it in CSS?
Definitely check out OOCSS as well as the Natalie Downe talk both posted by in the comments already.
I can't overstate how highly I recommend Sass/SCSS. It's been mentioned already as "for Ruby". Yes, you need Ruby installed to use Sass/SCSS but you do not need to be working on a Ruby project to use it. You can run "sass --watch (directory name)" from the command line and sass will automatically compile your .scss (or .sass) files to .css files upon save. Even if you're scared of the command line I assure you, it's easy! If you're a TextMate user, there's also a great SCSS bundle here: https://github.com/kuroir/SCSS.tmbundle (it was enough for me to abandon CSSEdit for good)
One thing that hasn't been discussed in this thread yet is the organization of properties within a declaration block. It's a good idea to have an approach and stick with it. Alphabetizing the properties is one approach. I wrote about my preferred approach a couple years ago here: http://fordinteractive.com/2009/02/order-of-the-day-css-prop... (also check out the SitePoint discussion linked in the "Further Reading" section of the post)
I'll admit it's a personal preference, but as a team consideration I don't recommend the 'all properties on one line' approach. It's discouraged in other languages so why do it in CSS?
Definitely check out OOCSS as well as the Natalie Downe talk both posted by in the comments already.
I can't overstate how highly I recommend Sass/SCSS. It's been mentioned already as "for Ruby". Yes, you need Ruby installed to use Sass/SCSS but you do not need to be working on a Ruby project to use it. You can run "sass --watch (directory name)" from the command line and sass will automatically compile your .scss (or .sass) files to .css files upon save. Even if you're scared of the command line I assure you, it's easy! If you're a TextMate user, there's also a great SCSS bundle here: https://github.com/kuroir/SCSS.tmbundle (it was enough for me to abandon CSSEdit for good)
One thing that hasn't been discussed in this thread yet is the organization of properties within a declaration block. It's a good idea to have an approach and stick with it. Alphabetizing the properties is one approach. I wrote about my preferred approach a couple years ago here: http://fordinteractive.com/2009/02/order-of-the-day-css-prop... (also check out the SitePoint discussion linked in the "Further Reading" section of the post)