Updated WordPress.org Theme Requirements
To all devs who develop themes on WordPress.org. There is a new requirement that will go into effect within the next 6 months. You can read all the details here: https://make.wordpress.org/themes/2015/04/21/this-weeks-meeting-important-information-regarding-theme-options
Essentially, the WordPress.org themes submission teams is mandating that theme developers ONLY use the Customizer for options.
What does this mean for Redux users? Here are the terms:
In 6 months time, all options MUST be customizer based for themes submitted to WP.org. Redux may be used, but only under these conditions.
- TGM to recommend Redux installed as a plugin OR follow the (instructions to embed Redux in a way that is approved by WP.org)[http://docs.reduxframework.com/core/wordpress-org-submissions/].
- Redux panel must be disabled, and only the `customizer_only` argument used.
- Only Customizer field types may be used. Any field that isn’t supported by the customizer must be coded by the developer or not used.
These are the following field types that can be used in the customizer, but most cannot have advanced options.
Unfortunately this is beyond our control. You are welcome to voice your opinion if you feel motivated to do so here: https://make.wordpress.org/themes/2015/04/21/this-weeks-meeting-important-information-regarding-theme-options
It seems that any framework, aside from http://kirki.org, should not be used in WordPress.org themes. Please voice your opinion if you have one to the WP.org team.