The success of using PostCSS will be partially determined by how well your code comes across from existing processors such as SASS—this will come from planning and taking an iterative approach to converting code. We've covered a lot of tips and ideas to help with the process, so let's take a moment to review what we've learnt.

We kicked off with a look at exploring the conversion process, and covered some of the plugins we might use to help with the process. We then moved on to covering the Pleeease library, with a look at installing and configuring it before using it in a quick demo.

Next up came a quick discussion about why Pleeease may not be as useful as we first thought; we then covered using the PreCSS library as a better alternative for transitioning to PostCSS.

We then explored using PreCSS in some depth by working through making changes to a standard theme for WordPress—we discovered some of the tips and tricks we can use to score quick wins when making the initial changes. We then rounded out the chapter with a look at compiling our code, and checking it in a standard WordPress installation to ensure it is still working as we would expect to see it operating.

Phew, we've covered a lot! With careful planning and using an iterative approach, we can transition from using processors such as SASS, and move to using PostCSS. However, sometimes our code may not work as expected—there are a few places where our code may trip up, so we'll cover them in the next chapter.