Automatic compilation of Sass files

[ddeboer]

Zotonic automatically compiles LESS to CSS. At Driebit we happen to use Sass.

Would adding Sass support to the automatic compilation be useful for others, as well?

[mworrell]

+1 Sass is used by quite some people and adding support is easily done by handling the .sass extension. I would suggest to handle it in a similar way (config etc) as we do with Less.

[mworrell]

BTW maybe we could handle files extensible? Using a first notifier would be enough, as that would create a new file, which triggers another file-change notification.

[ddeboer]

A notification is a good idea. We also need to account for some config (e.g. inclusion paths, minification flags). It seems the LESS support already does so.

[mworrell]

LESS support works smoothly, so indeed just copy the behavior, but then for SASS.

The notification can be added later in a refactor of the file handling code.

[arjan]

I uses SASS all the time already with Zotonic, although I use the .scss variants and not the weird yaml sass syntax. SCSS works fine, all files in lib/scss automatically get compiled into lib/css.

[ddeboer]

Lol, Zotonic already compiles .scss. I’ll have a look at the current functionality and see if anything is missing there.

[Devenwel]

We do use some npm packages in gulp to transform the output in our sites, like postCSS/Lost, autoprefixer, so that would have to keep working as well.