Theme review team weekly notes The logs are…

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

Theme review team weekly notes

The logs are here:

https://wordpress.slack.com/archives/themereview/p1418752733002887

Notes:

Both weekly meetings are to be paused due to holidays, next one is the 6th January 2015.

During the holidays a lot of us are taking time out to spend with family and recharge. The rate of themes should slow down, but this is a notice that queues may be a little longer due to this seasonal time. We’ll all attack things in the New Year and hit the queues.

All new themes because of the requirement about translations should now have the translation-ready tag.

We’re going to be holding monthly Q&A learnups. Our first one will be on Options and the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. and have a panel arranged by @greenshady. This will be sometime in January. The next one, we are thinking should be accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility).

A big thanks to anyone that’s reviewed this year, we’ve come a long way as a team and every review matters.

Ulrich 3:07 pm on January 4, 2015

I hope you all enjoyed your holidays and were able to relax.

I have a small request. Could a mirror of the requirements/recommendations be added to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/?
The three reasons for this is
1. We can publicly track the changes.
2. It would allow the possibility for people to create Pull requests/Change requests which can be discussed upon. I personally would find it easier to create a PR(Pull Request) to make a change then try to explain what the change is that I would like to make. I would imagine that a PR would be also a good place to discuss new requirements so that we all see what the change is while we discuss it. Hopefully it will also help people who are unable to make it to the team meetings to have a say in the change to the requirements/recommendations.

Jumping to the learnups. I would be interested in learning how best to review JS and what to lookout for.

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication