With the recent change to WordPress.org requiring themes to use the WordPress Theme Customizer in their work, WordPress designers and developers have been talking about it and discussing it for several weeks now.
And rightly so: Many of us are fans of the customizer, many are not, some fall in between, and some wish that there was a compromise.
As far as I’m concerned, that’s fine (though maybe I’m biased because I tend to be a fan of the Customizer), but whatever the case, this doesn’t change the fact that there’s a lot of education that needs to happen around how to use the API – which isn’t terribly difficult (in comparison, to say, the Settings API) – and how to make the transition over to it.


