It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.

Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.

When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.

Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.

CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.

Using Bourbon Neat for building a grid. It's easy to implement and is added to the CSS rather than the html which keeps similar modules looking the same.

love me some less. been less styling for around 3 years. makes working with bootstrap and responsive website a breeze. so much power in the language.

Agile CSS is written in less.

Customise the UIkit Front-End Framework, because of that is used to create the application CSS. I prefer SASS but is equivalent.

[Free] We use this free Sass framework on just about any project that we work on.

CSS Preprocessor, used primarily for variables to ensure brand colour continuity.

We use Less to organize our CSS code with imports, variables, mixins, and more.

Replaced Foundation grid system with Bourbon Neat.