Wouldn’t it be amazing if there was a decent CSS solution?
Published: November 26th, 2008By decent, I mean a solution that doesn’t make your ‘application.css’ look convoluted after a week of development with more than two developers. I’m sure you all know what I mean by this, if you don’t, you probably have a solution that I’d like to hear about.
I came upon an interesting article that tries to bring organization to css. Sure, using Sass1 helps a bit, and you all know I’m an advocate of Haml/Sass but this isn’t what the article is about. It actually has an interesting strategy for organizing your CSS in a butchered “RESTful” label.
In short, the article proposes having stylesheets for every action; index.css, show.css, edit.css, new.css, show.css, and of course your main.css file.
This sounds like an interesting strategy, and I’m eager to try it out on a project. I have done something similar in the past, and I ran into the hassle of having to look through multiple files to find what I’m really trying to pinpoint in the CSS. However, that was before the days of Firebug, so this seems like a really plasuable solution.
How do you feel about this strategy? Have you done something like it? Do you put all your styles in one file or do you separate it out?
I’d really love to hear your thoughts.
- http://haml.hamptoncatlin.com/ [↩]
Ready. Set. Go.
In terms of the formatting, you're allowed to use markdown, textile, or basic html; it's truly up to you -- what strikes your fancy?
You don't have to worry about your e-mail address being sold to a russian-spam-mafia. I'm only going to use it for my own weird needs; like asking you out for a date on a lonely night of coding.