I was wondering whether there is unbearable overhead involved in
breaking css
into multiple stylesheets? I’m running lighttpd, and the following
article
discusses why one might want to do that:
My CSS is beginning to get a bit lumpy to digest in one glance and the
article(s) seem to make a cogent argument for separating functional
elements
out. I just wanted to make sure there weren’t any Rails or server issues
that would be problematic.
I was wondering whether there is unbearable overhead involved in breaking css
into multiple stylesheets? I’m running lighttpd, and the following article
discusses why one might want to do that:
My CSS is beginning to get a bit lumpy to digest in one glance and the
article(s) seem to make a cogent argument for separating functional elements
out. I just wanted to make sure there weren’t any Rails or server issues
that would be problematic.
We’re not in production yet, but I don’t see why splitting it up in
rails/lighty would be any different than splitting it up for any other
environment.
In our case, we put this at the top of our default layout:
Then for each controller we create
public/stylesheets/controller_name.css
file. For those few sections that don’t have specific styles we have
an empty style sheet.
Yeah, it’s one more file to download, but it will only happen once per
browser (for the most part).
Well worth the sanity I’d say…
-philip
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.