Right now all the css files are still in our old format where all css is mashed into one file modulename.css

as stated in the css guidelines http://drupal.org/node/1089868 all the files should be split up into
modulename.admin.css
modulename.theme.css
modulename.base.css

insted of having a 120 differnt patches that isnt gonna get simultanious in, it would make sense so we can all move forward and work in the same manner to get all this into the same big issue. its just about moving the css into the right files and give em the right names.

nothing else should change atm - all the sexy new markup /css / accessability etc stuff well deal with later.

issues included from the big css cleanup:
http://drupal.org/node/1089868
#1216970: Clean up the CSS for Book module

Comments

jacine’s picture

jacine
she/her
Location New York
commented
Issue tags: +D8H5

Looking forward to helping with this over the weekend.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented

Subscribe!

cosmicdreams’s picture

cosmicdreams commented

This issue sounds very interesting... How much knowledge is needed to separate out the contents these css files appropriately? I suspect that the administrative styles would already be namespaced to admin classes.

cosmicdreams’s picture

cosmicdreams commented

This issue really sounds like fun. I'll turn my attention to this after #865536: drupal_add_js() is missing the 'browsers' option get's committed

jacine’s picture

jacine
she/her
Location New York
commented
Status: Active » Closed (duplicate)

You know, I started to work on this and realized why I went and separated them into smaller issues in the first place. It's just too much to do in one... Too much to patch and too much to review. Since we already have an initiative page for this, and since every single individual issue has a very big summary in it now, I'm going to close this one.