Requirements project March 23

Our next project meeting will be on Thursday at 19:00

Channel: #themereview

We have a few more short term fixes to discuss:

There is also one recommendation that perhaps should be removed:
Themes may optionally unregister coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Widgets. This is allowed, but is it recommended?

As a reminder, we also have the Trello board.


Those who have time after the meeting are welcome to continue,  with the purpose of defining what a “Letting users decide” approach would be for the team. We need to define it before we can continue any productive discussion on the topic.


Child themes should not include the name of the parent theme.

Suggestion: Child themes may only use the parent theme name if both themes are made by the same author.

Suggestion 2: Remove it (again).

If the theme adds a footer credit link, there should only be one (link to The 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. does not count).

Suggestion: There can only be a single footer credit link, which is either the the Theme URI or Author URI (link to does not count).

Theme URI:

Using as theme URI is reserved for official themes.

This was brought up on slackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at this weekend:
“The purpose of the Theme URI is to point the user to a page specifically about the theme that we are hosting here on That means that the majority of the info on that page should about the theme that we’re hosting.”
“Theme URI needs to be a) under a domain you control, not “”, and b) unique to the theme. Not unique to the theme and version number or anything else, just unique to the theme. ”

Themes are not allowed to add a menu item to the WordPress admin bar.

I believe this is used in practice but it is not currently listed on the requirement page. Is this something that we want to add or is it something that we would consider allowing?

The screenshot should be of the actual theme as it appears with default options, not a logo or mockup.

Suggestion: The screenshot should be of the theme, not a logo or mockup. The screenshot may optionally show plugins, settings and templates. The user should be able to make the theme look like the screenshot.