While this is fine for development and debugging, it's a pretty big
performance hit for your users to download lots of CSS files.
Combining them into 1 large file results in a page that loads quicker
by reducing HTTP requests.
http://developer.yahoo.com/performance/rules.html#num_http
-Ryan
On Jan 22, 2009, at 2:13 PM, Sarah Atkinson wrote:
One thing I tend to do is instead of having all my styles in main.css
I will have a css folder and in it usualy something like main.css,
header.css, footer.css, maybe other things that are item specific like
menu.css, documenttable.css, sidemenu.css.
I use this so that it’s easier to find my styles when I need to and
I can
exclude some pages if they are not needed. But some I talk to think
everything should be in one very long css file.
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Ryan Doherty
[email protected]
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/