An introduction to PostCSS and how you can improve your CSS processing workflow
Use future CSS features NOW without changing much of your preprocessing workflow. Profit from a modular system that solves a lot of tricky problems exactly in the combination that fits your projects' requirements from autoprefixing to CSS bleeding edge if you need that.
Yet another front-end madness or actually helpful?We have been using PostCSS for a couple of new projects now and I want to give an introduction, talk about our learnings and why this is a good idea. It is a very fast and flexible system that you can use in the setup that benefits you most. Like you would do with ES6 and a transpiler to ES5 you can use PostCSS to implement future CSS functionality today. The transition from other preprocessors like SASS is actually fairly easy.
However there are also some other very interesting approaches to improve your workflow and CSS processing beyond what's possibly with less flexible systems like SASS or LESS. It is part of the whole node/npm ecosystem and thus leverages the power of a large community of JS developers writing plugins.
- how the system of many diverse plugins caters for many use-cases and personal preferences
- how to implement that into a front-end workflow
- how to transition from SCSS
- why it makes sense to be able to use CSS bleeding edge functionality TODAY
- the benefits and some issues with the young preprocessing system