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.

Ulrich 3:27 pm on October 26, 2016

Automation Meeting October 27

In the last meeting on October 14 not everyone was able to attend who are contributing. Here are the belated meeting notes from the last meeting.

There was an issue in WPCSWPCS The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the WordPress Coding Standards. May also be an acronym referring to the Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. that was causing the travis tests to fail when we used PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. master branch, This has been fixed and we have merged the latest into the TRT/WPCS develop branch. All travis tests should be passing again.
I have made progress with the pull request to modularise the restricted functions upstream in WPCS. Hopefully it will get merged till the next meeting in two weeks.
I have started rebasing Kevin’s pull requests and making updates to the inline docs and making changes from the code reviews.
We had a few questions but no major discussions.

Channel: #themereview | Time: Thursday at 14:00 UTC 14:00 UTC

The goal of the bi-weekly meeting is keep other informed on the progress of the project and discuss any issues.

The agenda for the 27th October will be

Short update from the contributors what they have worked on.
Define goals for the next meeting.
Discuss any open issues and/or pull requests that need attention.

Pinging @poena, @frankklein, @pross, @jrf, @shinichin, @miyauchi

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

The next meeting is on Thursday, November 10.

s: search
c: compose new post
r: reply
e: edit
t: go to top
j: go to the next post or comment
k: go to the previous post or comment
o: toggle comment visibility
esc: cancel edit post or comment