Draft of the Theme Guidelines based off the plugin ones. I’m not a theme expert so welcome any feedback from theme developers and others.
The ClassicPress Theme Directory is intended to be a safe one-stop source for all ClassicPress compatible themes for all types of user, from the non-technical end-user to the developer.
The following rules are intended to provide transparency around the theme submission process for developers who submit their themes to the directory; further the rules aim to provide consistency and a level playing field for all developers.
If you have suggestions on improving the rules, or questions about them, please contact the theme moderators at [email protected].
All developers, users with commit access and all who officially support a theme are expected to follow the ClassicPress Theme Directory Rules.
- All developers will ensure their contact information is accurate and up-to-date.
- Developers must take a security first approach to their themes and ensure their themes are as secure as possible.
- It is strongly recommended that additional functionality such as sliders, shortcodes, custom post types and so on, be available in recommended or bundled plugins rather than in the theme itself as themes should handle appearance rather than functionality.
- Integration with update servers which allow themes to update to new versions (such as Update Manager) is not included in this rule, but update services must not collect identifiable.
- Free/Freemium/Premium themes are all welcome in the ClassicPress Theme Directory, but must be clearly identified as such in the description. Software-as-a-Service must be categorized as a Premium theme.
- Free - completely free, un-crippled, and not soliciting in any way.
- Freemium - some functionality free, but some requiring payment to the theme developer.
- Premium - paid, with no functionality available otherwise.
- All Free Themes must be compatible with the GNU General Public License; using the same license as ClassicPress (GPLv2 or later) is strongly recommended, but any GPL-compatible license is acceptable.
- Where a theme includes GPL-licensed code, the theme must fully adhere to the GPL license.
- Developers are solely responsible for the content and actions of their theme and must not do anything illegal, dishonest, or morally offensive, including exploiting loopholes in the Theme Directory rules. Furthermore, developers must respect trademarks, copyrights and project names; including such terms in the theme name may be acceptable depending on use, but never at the start of the name.
- Only completed themes are acceptable for submission to the Theme Directory; incomplete or misleading submissions are not permitted.
- Each time code is updated in the repository, the version number must be incremented; the use of Semantic Versioning 2.0.0 is strongly recommended. Frequent updates are not acceptable and will be seen as an attempt to game the search results; only release ready code should be committed.
- ClassicPress ships packaged with libraries such as jQuery, Atom Lib, SimplePie, PHPMailer, PHPass, etc.; themes must not include their own versions of any standard libraries.
- Developers will act in good faith and will not restore code they were previously asked to remove or write code to circumvent the rules.
- The developer will maintain their own GitHub repository for each theme which will include a stable version of the theme (as defined by the creation of a release).
- It is recommended best practice, but not required, that a release zip is included in a release (added in the Attach binaries by dropping them here or selecting them section).
- It is recommended for new themes that the theme folder/slug contain a vendor prefix. For example, a theme called THEME should have a folder of vendor-theme where vendor is the developer's unique prefix.
- Code must be human readable. Obfuscating or encyrypting code by use of systems or techniques such as p,a,c,k,e,r's obfuscate feature, uglify’s mangle, ionCube's encryption or unclear naming conventions such as $abc123, is not permitted in the directory.
- Publicly facing pages and files, such as Readme files, must not be used to spam users or game search results.
- Only critical or highly important notifications should be displayed outside of a themes settings pages and must be dismissible; adverts are **not** permitted outside of the Theme settings pages.
- Themes must not include credits or links on the public facing site without explicit opt-in permission from the user. Free themes may not require permission for the theme to function.
- ClassicPress will maintain the Theme Directory to the best of our ability, but reserve the following rights:
- To update the rules at any time.
- To suspend or remove a theme from the directory for breach, in word or spirit, of the Theme Directory rules.
- To allow new, active, developers to take over an orphaned theme (see adoption rules for further details).
Failure to follow the rules, or respond in a timely manner, will result in a theme being suspended from the directory until such time as the issue has been resolved; repeated failure to follow this rule may result in all a developer’s themes being removed from the directory and the developer banned from future submissions.
If you are uncertain whether a theme might violate the rules, please contact the theme moderators at [email protected].