We are a group of volunteers who review and approve themes submitted to be included in the official WordPress Theme directory. The Theme Review Team maintains the official Theme Review Requirements, the Theme Unit Test Data and the Theme SnifferpluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
When running a review session, we recommend that you first present the team and what we do, and introduce contributors to the Theme Review Team’s blog on https://make.wordpress.org/themes/.
During the introduction you will not need to or have the time to go through the entire requirements page, but emphasize that we review license and security first, before design.
After this short introduction, a lot of your time as a group leader will likely be spent helping people set up a local environment, which is step 4 of the Become a reviewer guide.
Set up a local installLocal InstallA local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. of WordPress.
When this is done, the contributors need a theme to review.
-Normally when someone starts reviewing a theme, they are assigned to a ticket in the themes TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., they post a review, and wait up to seven days for the theme author to reply.
We know that this format may not be suitable for a contributor day where the time is limited and where contributors may want to meet and try different teams during the day.
-Contributors should not be expected to complete a full review or to feel pressured into having to continue working on their ticket after the contributor day is over.
We recommend that you either:
Select a theme from the top of the queue, and review the theme together as a group. Make sure that everyone is included in the discussions.
Let contributors pick a theme each from the queue, but without being assigned to the ticket. By leaving the ticket status as new they will be able to add the result of their review, but will not need to do the follow up review. Contributors can also pair up and review a theme together.
Let contributors request a theme to review via the Theme Review SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. -Depending on who is online to see the request, this may take some time, so we encourage organizers to prepare ahead of time and request a couple of tickets to review before the contributor day starts.
Trac tickets that have been assigned during a contributor day will often need to be reassigned, so we would like to ask that you create a list of wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ usernames (or a list of ticket numbers) and send them via slack to either:
We would love to hear what we can improve to help contributors get started, if you are able to write down frequently asked questions about the process, the requirements or anything else, that would be very helpful.
