Web Developer, Accessibility & Sustainability evangelist, Human.
The new WordPress Editor (codenamed Gutenberg) is amazing as it allows users to build rich and beautiful interfaces with minimal effort. But it comes with a lot of styles and logic bundled-in, and I happen to have strong feelings about that, most of them negative ones. why would anyone enqueue styles for a button block, or a gallery block if a page doesn’t use them? We should all strive to build a more sustainable web, so that needs to change.
While refactoring the Kirki framework for v4.0, I needed to hijack the get and set functions from the JS API in order to apply some custom logic, so this is just a quick post to show how you can do that.
Create and enqueue a JS file in the customizer, and add this code in there:
17 February 2019
This year Kirki got 5 years old and broke the 2 million downloads barrier.
It was a big year with a lot of improvements in all areas of the plugin.
I wrote a lot of code, replaced a big part of our old codebase and there were major refactors across the board. As a developer I grow through Kirki, I discover new techniques and strive to improve it all the time.
However, while working on the Kirki plugin in 2018 one thing became evident. Things need to change. Kirki can’t move forward in its current form. It is bloated with a lot of code that the majority of theme developers will never use, or code that they use and I wish they never did (like for example using the customizer-styling module).
25 February 2018
Accessibility is one of the hardest things to accomplish on a site. One of the confusing things when trying to make a website accessible, is choosing the right color for your links.
17 February 2018
In the previous part of this series we saw a comparison of using the WordPress Customizer API and the Kirki shorter syntax to take care of CSS outputs & postMessage scripts generation.