Timo

I use find and replace all so it takes just a sec. to change all 40.

Jan

Timo - I'm with you on this one. 

I have emptied the default.css file but added an admin.css file for the DNN specific styles.  These styles are only really important to authenticated sessions so save the rest of the users from that grief.

All my heavy lifting is done by skin.css since that is closest logically to the design. It also gives me the greatest control over switching skin styles like homepage, admin or public skins.

I also empty portal.css and use it only to override tab/id specific styles like background images.  Some site wide styles can live in portal.css but i find the maintenance is much easier if the bulk is in skin.css.

My next step is to remove default.css and portal.css all together and save the extra server requests.

Timo Breumelhof wrotePersonally I don't like that, CSS is supposed to make life easier....
One of the advantages of CSS should be: Change the font in one place and the whole site.....

Or is there anybody that has another solution for this
(if you agree it's a problem in the first place)?   

It's the proverbial double-edged sword.  The default is there so that required CSS doesn't get missed by the designer of a skin, and to provide a base CSS.  But a skin designer who really wants the control will have to double the default.css in the skin to control everything.  Your option of it being an admin choice to use or not use the default.css, or even better to change the location of the default.css to a skin's folder, is sound.  The question is, will it be worth the modification to core behavior to satisfy this desire?  Personally, I don't see a performance difference when replicating all the default.css elements into the skin.css file, but I don't have any sites with enough traffic to really tell.  Is there a reason to do this other than convenience?

Jeff