19th April Team Meeting

Welcome to the Themes team!

We are a group of volunteers who review and approve themes submitted to be included in the official WordPress Theme directory.

We do license, security, and code quality reviews.

We help build and maintain default themes.

The primary focus of the team is to help theme authors transition to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based themes.

If this sounds interesting, read more about the team here. Check out our guide for new reviewers and the frequently asked questions.

Handbooks and review requirements

The team maintains the official Theme Review Requirements, the Theme Unit Test Data, and helps the documentation team with the Theme Developer Handbook.

Coding standards and plugins

We maintain the WPThemeReview Standard for PHP_CodeSniffer, the Theme Sniffer plugin and Theme Check

Code Packages

We have code packages for themes available for use on Github and Packagist

Communication

Meet us in the #themereview SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

Meetings:

Twice monthly at Tuesday @ 15:00 UTC.

#themereview

Admin notices

The primary focus of the meeting was on admin notices, particularly whether themes could display a delayed notice to users to ask for a review. The result of this discussion is that this is currently OK if the code follows all existing guidelines (e.g., correct capability check, make sure the notice can be dismissed, and anything else that would fall under the requirements).

The biggest takeaway from the discussion is, perhaps, that we should all continue to focus on making a great user experience. Whenever you add something to a theme, it should be for the user’s benefit. Keep that in mind when creating themes.

Following up on reopened tickets

Both the original reviewer and the admin who reopens a ticket should follow through with the items that an admin notes. The admin queue can quickly get backed up when we’re not doing this.

Additionally, admins who reopen a ticket should make sure to set tickets back to the “reviewing” state. Do this by entering the original reviewers username as the reviewer after reopening.