Some themes support including a local.css as a last step - this allows the end user to override styles in one place and allow easy upgrades when new versions come out with fixes.

The Acquia Prosper theme does this, just as an example. Thanks!

Comments

onejam’s picture

onejam commented

I think it would be better to create sub theme instead if users want to override styles. This way they only update the base theme without losing their changes.

verta’s picture

verta commented

I agree, a subtheme is the "better" way, if more complicated.

It's a lot easier to mod the CSS file than set up a subtheme, and the path of least resistance is the more tempting one!

verta’s picture

verta commented

This is what I was referring to:

http://drupal.org/node/680780

#680780: request for local.css or use of style.css as the local.css

Adding a call to a file callse local.css in the .info file lets the theme user override styles in a manner that can survive an upgrade. To update to the latest theme, just download it. Some themes include a file for local-sample.css with instructions to rename/copy the file to local.css and add style overrides.

The browser seems to not show errors if the local.css is called in the .info but does not exist.

It's turning out to be especially helpful when adding definitions and overrides for styles used by external code like TinyMCE.