Lots of small CSS files or one big one with sections - from a code-quality standpoint.

tags:

views:

71

answers:

1

+1 Q:

Lots of small CSS files or one big one with sections - from a code-quality standpoint.

I'm asking this question purely from an ease-of-development standpoint.

Performance is not a consideration, because we will have a build process that combines and compresses all our CSS files into a single file for release and then compresses it.

But which will be easier for a team of front-end developers to work with? Multiple files or a single file that is separated into distinct sections through comments?

+4 A:

If you're going to join and compress all the files at a later stage - I would most certainly split them into multiple files and organise them accordingly.

Check out how jQuery UI organise their CSS files, they have about 7 CSS files, and 1 main file which imports all 7 using the @import statement. This might be useful to you so you don't have to have 7 <link rel="stylesheet" /> references.

Also make sure you order them accordingly so that any overrides are always at the bottom.

Good luck

Marko

Marko 2010-07-02 04:11:03

Thanks Marco. I'll have a look at the jQuery files and how they're organized; they sound like a good setup to follow.

jonathanconway 2010-07-02 04:20:04

Your welcome - I found the files in my custom UI package in the folder development-bundle -> themes -> no-theme

Marko 2010-07-02 04:22:45

but @import is not advisable for performance http://developer.yahoo.com/performance/rules.html#csslink

metal-gear-solid 2010-07-06 13:17:21

"If you're going to join and compress all the files at a later stage...."

Marko 2010-07-06 19:23:41

ansaurus

tags:

views:

answers:

Lots of small CSS files or one big one with sections - from a code-quality standpoint.

related questions