Part of the CSS Cleanup: http://drupal.org/node/1089868

Overview of Goals

  1. Make it easy to remove unwanted design assumptions in the theme layer, while maintaining critical functionality (such as functional JavaScript widgets).
  2. Prevent uneeded administrative styles from loading on the front end.
  3. Give modules the ability to include a generic design implementation with their module, without burdening themers.
  4. Make CSS and related markup more efficient and less intrusive to improve the themer experience.

The CSS Clean-up Process

Use the following guidelines when writing patches for the core issues listed below.

  1. Put CSS is in the appropriate file: CSS should be moved to separate files, using the following
    name spacing conventions based on their purpose:
    module.base.css
    Should hold structural and behavior related styling. CSS should be coded against the Stark theme. The absolute bare minimum CSS required for the module to function should go here. If there is no CSS required, this file should be omitted.
    module.theme.css
    Should hold generic design-related styles that could be used with Stark and other themes. It's where all design assumptions like backgrounds, borders, colors, fonts, margins, padding, etc, would go.
    module.admin.css
    Should hold styles that are only applicable to administrative pages.

    To see an example of this in practice, look at Drupal's system module.

  2. Remove Assumptions: Styles that make too many assumptions, introduce superflous margins, padding and add things like font settings are not necessary and don't belong in core module CSS files. In cases where core themes depend on these properties, they should be moved to the CSS stylesheet of the respective theme.
  3. Reduce Selector Specificity: CSS code that resides in modules should be written in a way that's easily overridable in the theme layer. To improve the Themer Experience and make core CSS more efficient, CSS selectors should be made as general and short as possible. For example:
    • Use .style {} over div.style {} where possible.
    • Use .module .style {} over div.module div.somenestedelement .style where possible.
  4. Don't use IDs in selectors: Use of ID's in core CSS selectors requires more specificity in the theme layer, making it harder and more annoying to deal with. It makes achieveing consistency in complex design implementations much harder than it needs to be. We need to stop making life hard for theme developers.
  5. Don't be afraid to change markup: There's lots of overlap between using proper and semantic markup and doing CSS right. If you come across a case where CSS is being applied where using a more semantic elements would solve the problem, then change the markup in your patch to make it right. For more information, see the Drupal 8 Markup Gate rules.
  6. Start with Stark and cross-browser test.
    1. "Design" markup and CSS for the Stark theme.
    2. If applicable, adapt the styles to match the core themes afterward.
    3. Finally, test the changes in all supported browsers and ensure no regressions are introduced.
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jvc26’s picture

Assigned: Unassigned » jvc26
Status: Active » Needs review
FileSize
1.82 KB

Patch attempting to close this issue attached. Comments/review please.

jvc26’s picture

Corrected patch - prior patch added a stylesheets reference to file.info, new one replaces the old reference to the stylesheet in file.module.

jyve’s picture

Reviewed this patch, and looks good to me.

A patch for the image module css was added today, and I will advise there to also use base.css instead of admin.css so that these two modules are in line with each other.

xjm’s picture

Status: Needs review » Needs work
Issue tags: +Novice

Note that this patch will need to be rerolled, because the core directory structure for Drupal 8 has now changed. (For more information, see #22336: Move all core Drupal files under a /core folder to improve usability and upgrades). Tagging as novice for the task of rerolling the patch. Set the status back to "needs review" when submitting the updated patch.

If you need help rerolling this patch, you can come to core office hours or ask in #drupal-gitsupport on IRC.

karschsp’s picture

Status: Needs work » Needs review
FileSize
2.04 KB

Here's a re-roll for the /core move.

jyve’s picture

Status: Needs review » Needs work

After some discussion in another issue #1216970: Clean up the CSS for Book module I would think all this CSS should go into a file.admin.css instead of file.base.css.

karschsp’s picture

Here's a re-roll.

karschsp’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, clean-up-file-css.1216994.007.patch, failed testing.

karschsp’s picture

Status: Needs work » Needs review
FileSize
1.91 KB

Trying again.

jyve’s picture

Assigned: jvc26 » jyve
FileSize
1.94 KB

Just reviewed this patch and two things have been updated in the patch attached:

1. Added a file header in file.admin.css
2. Alphabetized the properties.

karschsp’s picture

Status: Needs review » Reviewed & tested by the community

Looks good.

catch’s picture

Status: Reviewed & tested by the community » Fixed

Looks good to me too. Committed/pushed to 8.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

miguelfrias’s picture

How can contributed to this section?

oresh’s picture

Status: Closed (fixed) » Needs review
FileSize
856 bytes

Really small patch for selector weight reduce. Just to make core cleaner.

xjm’s picture

Status: Needs review » Closed (fixed)

Create new issues, don't raise zombies.

xjm’s picture

Issue summary: View changes

Updated issue summary.