Contributing to WordPress Theme Review at WordPress.org
This is talk presented by our Founder/Lead Developer Sakin Shrestha at WordCamp Nepal 2014 #wcnp2014 . Special thanks to Tammie and Emil from WordPress Theme Review Team Admin for supporting the review process and providing guide for preparing slide.
This slide is useful for the people who want to know about WordPress Theme Review Team, Why and How to Join the Team? Process of Reviewing Theme. Posting your review finding is Ticket.
Fore more check out https://make.wordpress.org/themes
7. How Do I Join?
http://make.wordpress.org/themes/handbook/about/join-the-
team/
8. How Do I Join?
1. Register User Profile in WordPress.org
2. Subscribe to Blog
https://make.wordpress.org/themes/
3. Read Theme Review Handbook
https://make.wordpress.org/themes/handbook/
9. How Do I Join?
4. Join the #themereview Slack channel.
http://chat.wordpress.org
https://wordpress.slack.com/
5. Attend Weekly Meetings
Tuesday 18:00 UTC: Team Meeting
Thursday 18:00 UTC: Mentoring Meeting
12. Theme Unit Test
http://codex.wordpress.org/Theme_Unit_Test
Install WordPress Importer Plugin & Import test data
https://wpcom-themes.svn.automattic.com/demo/theme-unit-test-data.
xml
14. Developer Plugin
https://wordpress.org/plugins/developer/
1. Theme for a self-hosted WordPress installation
2. Install the Following Plugins
- Theme Check
- Regenerate Thumbnails
- RTL Tester
- Monster Widgets
- Debug Bar
- Log deprecated notices
15. Request a Ticket
https://make.wordpress.org/themes/
Click “New Reviewers”
For now, request ticket in Trac Ticket Request Queue
https://make.wordpress.org/themes/trac-ticket-request-queue-fall-
2014/
Post Username and Mentor (Optional)
17. Required
1. Theme Check Plugin
2. Log Depreciated Notice
3. PHP & Script Errors
4. Theme Tags
5. Theme URI & Author URI
6. Check License ( Must be 100% GPL Compatible)
7. Premium Theme Shop should be selling under GPL to be in
the WordPress.org repo
8. Footer Credit Links ( Only one – Author/Theme URI )
9. Screenshot should be a real image not a logo or mockup.
10. Plugin Territory
18. Required
11. Miscellaneous or unused files
12. Scripts & Styles ( No Hard Coding)
13. No analytics or tracking
14. Translation, Text Domain, Function Prefix
15. Proper Core Functionality ( Use Core Functions)
16. Sanitation, validation, escaping of inputs and outputs
17. Save option in single array
18. Use sane defaults & No default setting values in database
19. Theme names must not use: WordPress, Theme
20. Themes are must spell “WordPress” correctly in all public
facing text: all one word, with both an uppercase W and P.
19. Required (Automated)
1. No shortcodes, no custom post types and no custom
taxonomies
2. No removing or modifying non-presentational hooks
3. Disabling the admin tool bar
4. Theme settings page under appearance
5. Themes are required to declare their license explicitly using
the license and license uri header slugs to style.css
20. Recommendation
1. Backwards compatibility
2. Theme documentation
3. Accessibility
4. Theme unit test
5. Theme Check plugin info notices
6. changelog.txt for changelog
21. Post Review in Ticket
1. Hello and the welcome wrapper
2. Write your output
- Required
- Recommendation
- Info and Notes
3. What Next
- If theme meets all Requirements, then set it as Approve
- If theme doesn’t meets all Requirements,
- Ask to fix it and upload new version
- Leave the ticket open
- Close the ticket as Not Approved only when theme
author doesn’t response within 7 days
- Then Theme Review Admin/Key Reviewer will check
your review and either push live or reopen is found issues
22. What Next
Promotion to WordPress Theme Reviewer
Learn the Queues
https://themes.trac.wordpress.org
Updates & New
Start Reviewing Independently
23. Contribute in other ways
1. Theme Check Plugin
- https://github.com/Otto42/theme-check
2. Become a Mentor
3. Talk about Theme Review in Meetups and WordCamps
24. Thanks, any questions?
Blog: http://sakinshrestha.com
Email: info@sakinshrestha.com
Twitter: @sakinshrestha