@mattfarina @itsmisscs and I gave a 2 hour at DrupalCamp NY and I’m sure she’ll tell you the same thing about the command line.

@mattfarina sandcamp.org/include-sass. Very fast and high level; had spent the entire weekend in a more or less continuous Sass BoF.

@mattfarina Right, but they all either require the Gem, or don’t work as expected.

@mattfarina I invite you to one of my Sass sessions. Most front end devs glaze over the moment I mention the command line.

@davereid Haha. An Internet for you sir. //@mattfarina

@mattfarina …doesn’t know module/theme paths, making it hard to share now w/only Ruby

@mattfarina Ultimately, my want is for /all/ Drupal CSS to be written in Sass so all can share and make it easier for us. Compass also…

@mattfarina Not all front end themers can. There are entire swaths of themers who /only/ know CSS and Sass would benefit them greatly.

@mattfarina There should never be a reason to compile on Prod after an initial push, so that should be moot.

@mattfarina config.rb

@mattfarina To remove the barrier to entry of the Ruby to using Sass for Drupalites. No GUI system I’ve seen can deal w/requires w/o editing

@mattfarina Can compile as part push to Prod.

@mattfarina That’s a fair question. The real question, though, is what would trigger CSS to compile on Prod besides deving on Prod?

@mattfarina No, still learn Sass, just substituting Compass’s ‘require sassy-buttons’ for template.php and hook_partial_include().

@mattfarina Only if you compile the CSS on every page call instead of caching results and compiling when needed.

@mattfarina The Ruby gem doesn’t move fast enough for that to be a huge concern, and we deal wit that already with jQuery.

@mattfarina Could have a hook_partial_include(‘module’, ‘{name}’, ‘{dir}’) for themes.

@mattfarina Partials w/same name are easy to deal with as they are unique per folder per module. Always call partials by folder/name.

@mattfarina Correct, but relying on a PHP library for a PHP system is easier to do than a Ruby gem (which the GUIs still need)

@mattfarina Also, not saying it’s the Drupal way, saying it’s a solution to getting more of Drupal to use Sass. Esp. Windows people.

@mattfarina …would allow for Sass-based Drupal sub themes to work much easier w/sharing of functions/mixins/variables/extendables

@mattfarina …allowing Drupal to leverage its module/theme system and drupal_add_css as an alternative to Compass’s ‘require’. Also…

@mattfarina If all Drupal CSS files got compiled through Sass, any partials/selectors/Sass in the stack could be shared with any other…

@mattfarina To remove external dependencies to use Sass w/Drupal.

@mattfarina …Sass. Also opens up, in Drupal anyway, the ability for better CSS compression and very easy partial sharing.