For those from the #SassTalk who are interested in learning about Sass from the community, check out @SassBites youtube.com/user/sassbites

@dandineen Susy Next became Singularity 1.x and Susy 2.x after some internal discussions. @sassxsw @mbarker_84

RT @chriseppstein: #SassTalk If you like importing directly from node modules, you can use Eyeglass with node-sass.

github.com/sass-eyeglass/eyeglass

@liakamb I use github.com/at-import/toolkit#dry-mixins to create encapsulated mixins/extends for components and modules. Then can reuse as needed.

@sara_ann_marie …to not misappropriate the Sass brand and care that how discussions are framed and marketed is important.

@sara_ann_marie I would agree, except given the size and age of the Sass community, and the influence of ALA, IMO it’s ALA’s responsibility…

@sara_ann_marie @chriseppstein is a good person to talk to about the Sass community at large and the the Sass brand, as it is.

@sara_ann_marie …isn’t great and today wound up upsetting a bunch of the community.

@sara_ann_marie Not saying that either, just suggesting that billing something as Sass and it not being about that/having incorrect answers…

@sara_ann_marie Which is fair. Unfortunately, a bunch of the questions were about tools and many of the answers were incorrect.

@sara_ann_marie Those are all great questions and need to be answered. The anxiety is w/using the @SassCSS name for a general Prepro talk

@sara_ann_marie Many of the same questions could have been answered, but by people more familiar with Sass at scale.

@sara_ann_marie There are lots of exciting things happening in the space especially w/Libsass, Eyeglass, and Sass 4.0 roadmap

@sara_ann_marie As the hashtag was #SassTalk and the title was about Sass, I’d have liked it to be a discussion on Sass.

@sara_ann_marie I understand, and that’s an important convo to have, but the convo centered mainly on Sass/PostCSS/vanilla CSS

@sara_ann_marie …specifically called out in it’s title.

@sara_ann_marie Sorry, just trying to get across a the feeling of many in the Sass community about the perception of this talk as Sass was…

@alistapart Not just my issues/preferences, just the one being vocal about it.

@alistapart Well if it’s a discussion about Sass, more Sass advocates should be involved. I’ve got brand new designers who use Sass more.

#SassTalk Gulp/Grunt/Broccoli are all task runners, do the same things in different ways. Yeoman helps scaffold out new projects.

@alistapart So, the title was linkbait then? Most questions are about Sass specifically, so I think I’m not the only one w/that expectation

@alistapart Well, except this was billed as a @SassCSS talk, not a general CSS pre/post processor talk.

@alistapart There are a large number of @SassCSS community organizers and code maintainers who’d disagree.

#SassTalk LiveReload or my preference @Browsersync are amazingly helpful tools for working across multiple browsers and devices all at once.

#SassTalk Eyeglass and Node-Sass-Import-Once allow you to bring in 3rd party modules too. Not unique (or new in) to PostCSS