The WordPress Themes Team operates as a dedicated collective of volunteers responsible for evaluating, testing, and approving submissions destined for the official WordPress Theme Directory. Beyond directory intake, the team maintains core default themes, establishes rigorous review criteria, and provides developer documentation. Because the second Tuesday meeting of the month was cancelled, the session on July 28, 2026, serves as the primary operational gathering for the team.
Understanding the WordPress Themes Team Mandate
The core responsibility of the WordPress Themes Team revolves around maintaining strict licensing, security, and code quality standards across all submissions to the official directory. Reviewers evaluate incoming codebases against the official Theme Review Requirements to ensure they adhere to core WordPress coding standards, accessibility benchmarks, and structural integrity practices. Additionally, the team champions the continuous transition of the broader theme ecosystem toward block-based paradigms, helping authors modernize classic templates into full-site editing compatible experiences.
Meeting Logistics and Schedule for July 28, 2026
The Themes Team holds regular syncs twice a month on the second and fourth Tuesdays. Due to adjustments in the early part of the month, the July 28 meeting functions as the first official session for this cycle.
- Date and Time: Tuesday, July 28, 2026, at 15:00 UTC
- Platform: WordPress Community Slack
- Channel: #themes
Participation requires a registered WordPress Slack account. Developers, theme authors, and aspiring reviewers are encouraged to join the channel ahead of the scheduled time to review pinned resources and participate actively in the discussion.
Standardized Review Tooling and Standards
To maintain consistency at scale, the WordPress Themes Team develops and maintains critical automated tooling used by both internal reviewers and independent authors. Utilizing these tools during local development drastically reduces queue wait times and catches compliance violations before submission.
- WPThemeReview Standard: A dedicated ruleset for PHP_CodeSniffer designed to enforce WordPress-specific coding practices, security checks, and best practices within theme codebases.
- Theme Sniffer Plugin: An automated analysis plugin that scans theme files directly within a WordPress installation for deprecated functions, coding standard errors, and potential security issues.
- Theme Check Code Packages: Verification packages available via GitHub and Packagist to integrate automated static analysis into continuous integration (CI) pipelines.
Transitioning to Block-Based Themes
A primary objective for the Themes Team is steering authors away from legacy architectures toward block-based themes. This transition involves educating the community on theme.json configuration, block templates, pattern registrations, and global styles. Reviewers look for proper utilization of native WordPress APIs rather than custom framework implementations that duplicate core functionality. Theme authors migrating older layouts must adapt to markup-driven template structures, ensuring seamless compatibility with future core updates.
Documentation, Resources, and Unit Testing
High review standards require robust documentation and dependable testing environments. The team actively contributes to the Theme Developer Handbook, providing authoritative guidance on modern development workflows. Furthermore, the team maintains the official Theme Unit Test Data—a standardized dataset containing complex content structures, nested blocks, and edge-case typography. Authors must test their themes against this dataset to verify that layouts do not break under varied content scenarios.
Meeting Agenda Breakdown
The structured agenda for the July 28, 2026 session is designed to keep the community informed while prioritizing direct engagement from contributors:
- Weekly Updates: Reports on review queue backlogs, tooling updates, and progress regarding default theme maintenance.
- Open Floor: An open session dedicated to community questions, specific theme review roadblocks, and general ecosystem announcements.
Participants who wish to add specific discussion topics to the agenda are encouraged to leave comments on the official Make WordPress Themes post prior to the meeting start time.
How to Get Involved as a Reviewer
The WordPress Theme Review team relies entirely on community volunteers. Developers interested in joining the review queue must familiarize themselves with the official reviewer guide, understand the nuances of the Theme Review Requirements, and shadow experienced reviewers within the #themereview and #themes Slack channels. Contributing to theme reviews offers deep insight into core architecture, security best practices, and the evolving block editing ecosystem.
Frequently asked questions
When and where is the WordPress Themes Team meeting taking place?
The meeting is scheduled for Tuesday, July 28, 2026, at 15:00 UTC in the #themes channel on the WordPress Community Slack.
What tools does the Themes Team maintain for code quality?
The team maintains the WPThemeReview PHP_CodeSniffer standard, the Theme Sniffer plugin, and Theme Check code packages available on GitHub and Packagist.
How can I participate in the Themes Team meeting?
You need a registered WordPress Slack account to join the #themes channel at the scheduled time. You can also comment on the official meeting agenda post to suggest topics.
Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.
