Below is a list of things I want to accomplish in the next versions. The items on this list are in no particular order and at this point there are no ETAs or versions. This is just a rough draft of my goals regarding Kirki
I recently introduced a
kirkiDynamicControl object in Kirki - derived from the wp-customize-posts plugin. When a Kirki control extends that object we’re able to initialize the control not when the customizer loads, but when the control’s section is activated. This makes the initial customizer load a lot faster, but the actual markup for many controls is still added on load. By moving the markup to the JS files we’ll be able to render the controls only when they are needed instead of on load.
Abstracting the controls would allow us for example to create complex controls easier and more effectively.
typography control wouldn’t need to create everything from scratch.
Instead we’d add all input fields that consitute the typography control using the
kirki object, and everything else would be taken care of automatically.
Repeaters would be able to act as wrapper for complete control structures instead of wrappers for simple input elements.
Planned forfuture version
This module will be deprecated. It should not be part of the plugin’s core. We can provide it as a separate module that developers can add if they want it.