Submitting to the WordPress Theme Directory


Published on

Learn about the steps involved in getting a WordPress theme ready for submission to the WordPress Theme Directory. It covers the Theme Review Guidelines, WordPress development standards and the GPL requirements along with testing requirements. Everything you need to know about making your theme submission as smooth as possible.

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Submitting to the WordPress Theme Directory

  1. 1. Submitting to the WordPress Theme Directory Anthony Hortin#wpmelb @maddisondesigns
  2. 2. What is the Theme Directory?The Theme Directory is a great place to find freeawesome themes.Each theme has been thoroughly tested by theWordPress Theme Review Team so as to ensure ahigh level of standard.
  3. 3. Theme Review GuidelinesThe Theme Review Guidelines are maintained bythe Theme Review Team.It outline standards and practices for WordPressTheme development and design.
  4. 4. Theme Review GuidelinesCode QualityThemes must not generate any WordPressdeprecated-function notices, PHP errors, warnings,or notices, HTML/CSS validation errors, orJavaScript errors.
  5. 5. Theme Review GuidelinesCode Quality✓ Themes must not use deprecated functions✓ Themes must not support backward compatibility for more than two prior major WordPress versions✓ Themes must not have any notices, warnings, or errors when using WP_DEBUG in wp-config.php✓ Themes must not generate any JavaScript errors✓ Themes are required to use a ‘theme-slug’ as the textdomain for translation purposes
  6. 6. Theme Review GuidelinesPresentation vs FunctionalityThemes must not be used to define the generationof user content, or to define Theme-independentsite options or functionality.
  7. 7. Theme Review GuidelinesPresentation vs Functionality✓ Themes are required to have all public-facing text in English✓ Theme may optionally incorporate translation/ internationalization✓ Themes are recommended not to implement custom favicon functionality
  8. 8. Theme Review GuidelinesTheme FeaturesThemes are required to support proper WordPresscore implementation of all included features.
  9. 9. Theme Review GuidelinesTheme Features✓ Theme is required to incorporate the following WordPress core Theme Features: - Automatic Feed Links - Sidebars - Comments✓ Theme is recommended (but not required) to incorporate the following core features: - Navigation Menus - Post Thumbnails - Custom Headers - Custom Backgrounds - Visual Editor CSS✓ Theme must not incorporate Admin/feature pointers
  10. 10. Theme Review GuidelinesTemplate Tags and HooksThemes are required to implement WordPresstemplate tags and hooks properly.
  11. 11. Theme Review GuidelinesTemplate Tags and Hooks✓ Certain template tags and hooks are required to be included, such as: - wp_title() - wp_head() - wp_footer()✓ Standard template files are required to be called correctly, such as: - get_header() - get_footer() - get_template_part()✓ Themes are required to correctly enqueue all stylesheets and scripts: - wp_enqueue_style() - wp_enqueue_script()
  12. 12. Theme Review GuidelinesWordPress-Generated CSS ClassesThemes are required to support WordPress-generated CSS classes.
  13. 13. Theme Review GuidelinesWordPress-Generated CSS Classes✓ Themes are required to support certain css classes, such as: - .aligncenter - .alignleft - .alignright - .wp-caption - .wp-caption-text - .gallery-caption - .sticky - .bypostauthor
  14. 14. Theme Review GuidelinesTheme Template FilesThemes are required to utilise Theme templatefiles properly.
  15. 15. Theme Review GuidelinesTheme Template Files✓ Theme is required to include, at a minimum: - index.php - comments.php - style.css✓ Theme is recommended to include: - 404.php - archive.php - page.php - search.php - single.php - header.php - footer.php - sidebar.php✓ Theme thumbnail (screenshot.png) is recommended to be 600 x 450px
  16. 16. Theme Review GuidelinesSecurity and PrivacyThemes are required to implement Theme settingsproperly, to ensure proper data security, and toensure end user privacy.
  17. 17. Theme Review GuidelinesSecurity and Privacy✓ Themes are required to prefix all options, custom functions, custom variables, and custom constants with theme-slug (or appropriate variant).✓ Themes are required to validate and sanitize all untrusted data✓ Themes must not "phone home" without informed user consent
  18. 18. Theme Review GuidelinesLicensingThemes are required to be licensed fully under aGPL-compatible license.
  19. 19. Theme Review GuidelinesLicensing✓ Themes are required to be 100% GPL-licensed, or use a GPL-compatible license. This includes all PHP, HTML, CSS, images, fonts, icons, and everything else. All of the theme must be GPL- compatible.✓ Themes are required to declare their license explicitly✓ Themes must not clone the design of a past or present web site.
  20. 20. Theme Review GuidelinesTheme NameThemes are required to use appropriate ThemeNames.
  21. 21. Theme Review GuidelinesTheme Name✓ Themes are not to use WordPress in their name✓ Themes are not to use the term Theme in their name✓ Themes may use the WP acronym in the Theme name✓ Themes are not to use version-specific, markup-related terms (e.g. HTML5, CSS3, etc.) in their name.
  22. 22. Theme Review GuidelinesCredit LinksThemes are recommended to use credit links. Ifused, credit links are required to be appropriate.
  23. 23. Theme Review GuidelinesCredit Links✓ Themes may optionally designate Author URI and Theme URI in style.css and are recommended to provide at least one of these two links✓ Themes may optionally include a public-facing credit link in the Theme footer✓ Since Themes are GPL (or compatible), Theme authors are prohibited from requiring that these links be kept by Theme users
  24. 24. Theme Review GuidelinesTheme DocumentationThemes are required to provide sufficientdocumentation to explain the use of any customfeatures or options.
  25. 25. Theme Review GuidelinesTheme Documentation✓ Themes are required to provide end-user documentation of any design limitations or extraordinary installation/setup instructions✓ Themes are recommended to include a readme.txt file✓ In lieu of a readme.txt file, Themes are recommended to include a changelog, indicating version-to-version Theme changes.
  26. 26. Theme Review GuidelinesTheme Unit TestThemes are required to meet all requirements inthe Theme Unit Tests.
  27. 27. Theme Review GuidelinesTheme Unit Test✓ The Theme must meet all the requirements of the Theme Unit Test
  28. 28. Theme Review GuidelinesTheme ObsolescenceThemes are required to be kept current onceaccepted into the Theme Repository.
  29. 29. Theme Review GuidelinesTheme Obsolescence✓ Themes must be kept current once submitted, approved, and accepted into the Theme Repository.✓ Any Theme not updated to the current theme review process as of the most recent release of WordPress may be subject to temporary suspension.
  30. 30. Theme DevelopmentWhether you’re developing for the Theme Directory,a client or just yourself...It pays to have good code.WordPress provides you with a set of standards tofollow.
  31. 31. Theme DevelopmentTheme Development Standards✓ Use well-structured, error-free PHP & valid HTML WordPress Coding Standards:✓ Use clean, valid CSS CSS Coding Standard:✓ Follow design guidelines Site Design and Layout:
  32. 32. Theme DevelopmentTheme StylesheetAdd information about your theme into yourstyle.css file, in the form of comments./*Theme Name: Twenty ThirteenTheme URI: the WordPress teamAuthor URI: The 2013 theme for WordPress takes us back to the blog, featuring a full range of postformats, each displayed beautifully in their own unique way. Design details abound, starting with agorgeous color scheme and matching header images, optional display fonts for beautiful typography,and a wide layout that looks great on large screens yet remains device-agnostic and is readable onany device.Version: 0.1License: GNU General Public License v2 or laterLicense URI: black, brown, orange, tan, white, light, one-column, two-columns, right-sidebar, flexible-width, custom-header, custom-menu, editor-style, featured-images, microformats, post-formats, rtl-language-support, sticky-post, translation-readyText Domain: twentythirteenThis theme, like WordPress, is licensed under the GPL.Use it to make something cool, have fun, and share what youve learned with others.*/
  33. 33. Theme DevelopmentTheme StylesheetWhen specifying your tags in style.css, make sureto only use the allowed tags.
  34. 34. Theme DevelopmentCode FormattingPretty code makes for happy developers!Using Sublime Text 2, automatically format yourPHP to conform to the WordPress Coding Standards Tip:Easily search the WordPress Codex or lookup WordPress functions
  35. 35. Theme Development100% GPLThemes must be 100% GPL (or GPL-Compatible)This means ALL images, HTML, CSS, PHP, fonts,icons, JavaScript etc.Creative Commons is not GPL-Compatible
  36. 36. Oh, one last thing...
  37. 37. Spell “WordPress” correctly!!!✓ All one word!✓ Uppercase W!✓ Uppercase P!
  38. 38. Links to RememberWordPress Theme Review Team Review Guidelines Unit Test Coding Standards Coding Standards format. Similar format to this plugin readme sample your theme to the Theme Directory
  39. 39. Links to RememberGNU GPL v2.0 License font licenses icon sets Check Plugin. Make sure to test your theme before submitting Widget. A quick method of adding all core widgets to a sidebar
  40. 40. That’s all folks!☺Thanks! Questions?You can find me