CiviCRM Community Forums (archive)

The idea of extras.css is great, but wouldn't it make more sense if it were loaded from one of the custom directories so it wasn't overwritten every update? Could simply add a checkbox under the Custom Template directory settings, "Load extras.css from this directory as well?". Simple suggestion and almost not worth griping about but it always sucks to have extra steps when doing a simple update, and separating this from the core Civi css would fall more in line with the manner in which Civi handles almost all other customizations.

Might make sense and be easier to load an "extra" css file via an additional Resource URL setting (civicrm/admin/setting/url). We already support loading a custom copy of civicrm.css there. Defining an "extra / additional" css file there would provide an easy way to add stuff w/o needing to modify the entire civicrm.css file. We wouldn't care what the name of the file is. Or, you could potentially define a directory and the code could grab any .css file(s) that are present - so not limiting to 1 or N additional css files.

(Patch welcome if this idea also makes sense to you.)

Side-note: Some folks are defining additional css styles for Civi in their theme's css file(s). At least in Drupal, they are loaded on Civi pages, so this works pretty well (or at least that's what I've heard).