HTML and CSS Reference
In-Depth Information
… to this:
If you section and comment your CSS well enough, using a table of contents
and so forth, then you avoid the need to split up your CSS files, thus keeping
those requests down.
If you really want to break up your CSS into multiple style sheets, you can do
that — just combine them into one at build time. This way, your developers
can work across multiple files, but your users will download one
concatenated file.
Learning From Programmers
Programmers have been doing this for ages, and doing it well. Their job is to
write code that is as readable as it is functional. We front-end developers
could learn a lot from how programmers deal with code.
The code of my good friend (and absolutely awesome chap) Dan Bentley
really struck a chord with me. It's beautiful. I don't understand what it does
most of the time, but it's so clean and lovely to look at. So much white
space, so neat and tidy, all commented and properly looked after. His PHP,
Ruby, Python or whatever-he-decides-to-use-that-day always looks so nice.
It made me want to write my CSS the same way.
