Would it be possible to add a local.css line (stylesheets[all][] = css/local.css) to sky.info and include a dummy local.css file in the css directory as part of the distribution? For those of us using a local.css file it would eliminate a sky.info editing step after theme upgrades.

Comments

Jeff Burnz’s picture

Jeff Burnz commented

Yeah, I could do that, lets see if there are any objections, in some other themes I have a sky.custom.styles.css type file, but its actually commented out by default so still requires that one edit.

The only thing I have against loading this sort of thing by default is that the theme will load an empty stylesheet for those who never use it, although with CSS aggregation this is not really an issue.

tenken’s picture

tenken commented

Wouldn't the more correct path be to create a subtheme of Sky? I have a subtheme of sky that started as purely CSS overrides, and now "overrides" some of the template.php defined Sky functions.

Some customization is possible with the Color module -- etc. But one may as well use CSS Injector rather than a local.css.

Just a differing opinion on the matter. If you still supply local.css in your release(s), then versioning the theme locally becomes more problematic ...