• Code Quality:
    • Themes must not generate any Theme-Check Warning or Required notices. Themes must not generate any WordPress deprecated-function or _doing_it_wrong() notices, PHP errors, warnings, or notices, HTML/CSS validation errors, or JavaScript errors.
    • Themes must not provide backward compatibility for out-of-date WordPress versions (more than two prior major WordPress versions – currently, that means versions prior to WordPress 3.3), including using function_exists() conditional wrappers for current WordPress functions.
    • Themes must provide a unique slug for anything in the public namspace, including translation textdomain, all custom function names, classes, hooks, public/global variables, database entries (Theme options, post custom metadata, etc.)
    • Themes must provide all public-facing text strings in English.
    • Guidelines: Theme Check
  • Presentation Vs. Functionality:
    • Since the purpose of Themes is to define the presentation of user content, Themes must not be used to define the generation of user content, or to define Theme-independent site options or functionality.
    • Guidelines: Plugin Territory
  • Theme Features:
    • Whether implementing required, recommended, or optional features, Themes are required to support proper WordPress core implementation of all included features.
  • Template Tags and Hooks:
  • WordPress-Generated CSS Classes:
    • Themes are required to support WordPress-generated CSS classes.
  • Theme Template Files:
  • Security and Privacy:
  • Licensing, Theme Name, Credit Links, Up-Sell Themes:
  • Theme Documentation:
    • Themes are required to provide sufficient documentation to explain the use of any custom features or options.
  • Theme Obsolescence:
    • Themes are required to be kept current once accepted into the Theme Repository.
  • Accessibility:
  • WordPress Trademark
    • Themes are must spell “WordPress” correctly in all public facing text: all one word, with both an uppercase W and P.