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 blockBlockBlock 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.
A new default theme is usually included in the last major releaseMajor ReleaseA set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. of the year.
The lead designer and lead developer are part of the release squad. The design is selected and approved by project lead Matt Mullenweg before the development of the theme starts.
For the past 3 years, the development of the theme has been open to all contributors.
You can suggest features that you want the theme to include.
The theme follows the same release cycle as WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. A feature suggestion needs to be submitted as early in the release as possible for the developers to have time to consider and work on implementing your suggestion.
The earlier the testing starts, the better chance that theme is released with as few bugs as possible.
Testing the accessibilityAccessibilityAccessibility (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) of the theme should be prioritized.
Every theme needs a theme description. Copy also needs to be written if the theme includes starter content and blockBlockBlock 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. patterns.
It is important that all text that is used for custom options and instructions is relevant and easy to understand.
The default theme has an official support page which needs to be complete for Release CandidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. 1.
When writing text for the theme, use sentence casing and not title case.
When possible, keep texts consistent with previous default themes.
Decide how often and when to hold meetings. Meetings take place in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. in the #core-themes channel. You can schedule separate bug scrubs or you can do this as part of the meeting. You can also decide if you want to post meeting agendas before each meeting.
Instead of using private channels, try to keep discussions public in the #core-themes channels so that more people have a chance to get involved and contribute.
You will need access to the Core blog to be able to post updates, meeting agendas or calls for testing.
Access to using the /here command for the #core-themes Slack channel is needed for meetings.
To work on theme related TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. issues, you may also need increased “bug gardening” privileges for the Core Trac.
The default theme needs to be accessibility-ready, and aim to comply with WCAGWCAGWCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/.. Accessibility needs to be included in the design and development process from the start and can not be added at the last minute.
If you are not already familiar with the guidelines for the theme directory, please read them here.
The theme development takes place in a dedicated GitHubGitHubGitHub 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/ repository that is part the WordPress organisation. You will need administrative rights to be able to invite contributors and in turn grant them the rights they need to help you with the development and triage.
Development is moved to the Core Trac at a point that you decide. With the final release of the WordPress version, the GitHub repository is archived.
To make sure that all contributors receive credits (props) for their work, you need to keep a list of their WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ usernames. In the GitHub repository, this can be saved in a Contributors.md file. Example: https://github.com/WordPress/twentytwentyone/blob/trunk/CONTRIBUTORS.md
The benefit of using GitHub is that you will see the result of the automated tests right away.
For Beta releases, you will add the patch/pull request to WordPress trunk.
To make changes during the release candidates, you need sign off from two committers. These changes should be bug fixes for things found during the RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge..
In the description of the pull request or patch, include the list of usernames that should receive props for contributing to the theme.
When the pull request has been made, contact a committer who can add the theme to the WordPress package.