I think it's a good idea, since it'll make the creation and maintenance of custom themes a lot easier. I'm assuming we'd divide the .scss files up into logical components so that a custom theme could swap out just the header for example, and keep everything else from the default theme.
We could include a generated .css file in git or maybe just each release. Then someone getting started still doesn't need to install sass and ruby. We'd have to remember to keep that generated file current though. On 8/9/12 6:34 PM, Rick Copeland wrote: > +1 from me > > On Thu, Aug 9, 2012 at 6:14 PM, Jenny Steele <[email protected]> wrote: > >> Right now, Allura's css is mostly in one big file. At about 2700 lines, it >> isn't very friendly to work with. The css that's currently in there was >> actually generated from a closed source package using Sass. What do you >> guys think about putting the .scss files in Allura and making that a part >> of the package? >> >> Originally, we decided not to use Sass in Allura because it would be an >> extra dependency to install and maintain. The benefit is it would make >> working with the theme or creating custom themes for new installations a >> lot easier. >> -- >> ==== >> This e- mail message is intended only for the named recipient(s) above. It >> may contain confidential and privileged information. If you are not the >> intended recipient you are hereby notified that any dissemination, >> distribution or copying of this e-mail and any attachment(s) is strictly >> prohibited. If you have received this e-mail in error, please immediately >> notify the sender by replying to this e-mail and delete the message and any >> attachment(s) from your system. Thank you. >> >> > -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
