Welcome to the Theme Review 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.
Code reviews are a great way to learn more about developing themes and improving your own skills.
If this sounds interesting, read more about the team here. Check out our guide for new reviewers.
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, and the Theme Sniffer plugin.
Code Packages
We have code packages for themes available for use on Github and Packagist
Communication
Meet us in the #themereview Slack channel.
Meetings:
Twice monthly at Tuesday @ 17:00 UTC Second Tuesday in the month is open floor and the fourth Tuesday is with a fixed agenda.
Block Based Themes meeting twice monthly at Wednesday @ 16:00 UTC
Triage Meeting twice monthly at Wednesday @ 18:00 UTC
Important notice about Trac issues
If you are seeing this message: Missing or invalid form token. Do you have cookies enabled?
Go here: https://themes.trac.wordpress.org/ and login again.
When you brought up the idea of a new meeting, it was with the intent to give and take feedback, not to dictate what the “new way” would be.
But the above description and even the name of the meeting goes against what the core concept of a theme is.
By calling it “block based theme”, it implies that the theme must know something about content and how the editor works. But that is out of scope for a theme. The theme should be able to present the user’s content regardless of which editor is used or which page builder or even content from an external feed.
WP already has full site editing, in the Customizer, and themes have enhanced this for years. The new use of that term is biased toward the block editor since that’s all the rage. Why is the current Full Site Editing code outside the scope of the Customizer? What is the goal? Is it even something that makes sense for themes? (themes usually provide consistency across pages, but this new way is opposite of that)
Don’t we need a merge proposal? Or even a consensus on design before forcing these changes into core and having meetings about using experimental code as if it’s the only choice?
I’ve never seen a good description of the problem being solved by these “experiments”.
Hi Joy! To be clear, the purpose of this meeting is to provide a venue for sharing thoughts, concerns, and ideas around the future of themes. Your perspective is absolutely appreciated.
While the “Block-based themes” title does mirror the experimental theme specification in Gutenberg’s handbook, I’d like to stress that it’s meant to refer more generally to the role that themes play as WordPress becomes more infused with blocks. That experiment is just one potential starting point: One which I hope we will all try out, evaluate, and iterate on together during this meeting.
On a high level, full-site editing is meant to provide more flexibility to users than the Customizer affords today. You may find more details in this initial post + video about expanding Gutenberg beyond the editor, in case you haven’t read it:
http://wayback.fauppsala.se:80/wayback/20200307163132/https://make.wordpress.org/core/2019/09/05/defining-content-block-areas/
Thank you for sharing your perspective, and I hope to discuss more in the meetings.
Stoked for this 🙌 Super excited to see how far the community can push the next generation of themes!
Hi guys,
I’ll be there. There are too many questions, so at first I want to somehow orient myself and then precisely formulated questions will surely appear.