PostCSS essentially allows you to set up your own CSS preprocessor with the features that matter to you. It has a modular plugin-based architecture, which means that if someone comes up with a useful new feature, you can easily add it to your stack as a PostCSS plugin. PreCSS and PostCSS-cssnext are some of my go-to plugins.

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.

PostCSS handles compiling node-based CSS libraries, including BassCSS (the whole site is only ~85 lines of custom CSS). It also does auto-vendor-prefixing and support for CSS variables.

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.

We wrote a lot of flexbox and css that needed prefixing. PostCSS + Webpack was the best option here.

CSSNext, import, loaders, nesting. Components written using BEM style.

Used to minify and extend the CSS markup of the framework.