WordPress.org

Theme Review Team

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.

The Theme Review team maintains the official Theme Review Requirements, the Theme Unit Test Data, and the Theme Check Plugin.

We also engage and educate the WordPress Theme community regarding best practices for themes.

Interested in joining the Theme Reviewers team?

Great! The team is open to anyone who wants to help out, and the process is simple. To find out more just visit the Join The Team page.

Want to know more? There is a more information in the Theme Review Team’s Handbook and the Review itself.

Once you get a theme to review, you will also get a mentor to help you on the road to becoming a theme reviewer.

Weekly meetings

We use Slack for real-time communication. As contributors live all over the world, there are discussions happening at all hours of the day.

We have a project meeting every Tuesday at 18:00 UTC in the #themereview channel on Slack. The next one will be at Tuesday at 18:00 UTC.

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Justin Tadlock 6:50 pm on July 26, 2016 Permalink |  

    Meeting notes for 2016 July 26 

    We had a solid discussion based on this week’s agenda.

    Read the meeting transcript in the Slack archives. (A Slack account is required)

    Removing exception to hardcoded scripts guideline

    The first item was to discuss the removal of an exception to one of our existing guidelines when WordPress 4.6 is released:

    No hard coding of scripts and styles unless a browser workaround script.

    We will no longer be allowing browser workaround scripts to be hardcoded. The new guideline would be rewritten to become:

    No hard coding of scripts and styles.

    The reason to remove the exception is because WordPress has the wp_script_add_data() function for handling this. When WP 4.6 rolls out, that’ll be more than 3 versions for back-compatibility.

    So, it’s time to update your code if you have any hardcoded scripts remaining. You can find an example in the TwentySixteen theme.

    UX considerations for the feature filter

    @celloexpressions brought up the idea of making the “subjects” in the feature filter a drop-down. We’d like to see user testing and give time for the new subjects list to be used first.

    In our next tags iteration (next January), we want to consider overall improvements to the entire feature filter box and what can be done to make this better for users.

    Adding the review baseline to the handbook

    @sakinshrestha is getting his first project as a key reviewer.

    He’ll begin work on adding the review baseline to the handbook. This is to make sure theme authors are aware of how our new review flow works.

     
  • Ulrich 6:58 am on July 25, 2016 Permalink |  

    Agenda for 2016 July 26 

    The Theme Review Team holds a meeting weekly and we encourage all members to attend.

    Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

    Topic : Open discussion

    • We currently have an exception for enqueuing browser workaround script. Since WordPress 4.2, wp_script_add_data() exists, and browser workaround scripts now can be enqueued (see TwentySixteen). I would like to remove this exception once WordPress 4.6 is released which is planned for the middle of August.

    No hard coding of scripts and styles unless a browser workaround script.

    The meetings typically last 30 minutes. If time permits, additional topics may be discussed.

    If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

     
  • Ulrich 8:56 am on July 19, 2016 Permalink |  

    Agenda for 2016 July 19 

    The Theme Review Team holds a meeting weekly and we encourage all members to attend.

    Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

    Topic : Open discussion

    The meetings typically last 30 minutes. If time permits, additional topics may be discussed.

    If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

     
    • Rinku Y 3:52 pm on July 19, 2016 Permalink | Log in to Reply

      We have more new themes but less reviewer. now new theme need to wait for 5-6 moths to get start for review.

    • madriverweb 7:53 pm on July 19, 2016 Permalink | Log in to Reply

      Topic: Making WordPress.org as easy a choice as WordPress.com, Squarespace, Wix or Weebly. Background: I am a web developer who also hosts about 100 accounts, some of which use WordPress. Problems:
      1. Many of my clients have a preconceived idea that WordPress is harder to use than other platforms.
      2. With a setup that includes only the latest “twenty…” themes, they are either dependent on a web developer or have to browse an overwhelming number of themes knowing they are still only seeing a fraction of those available, without even getting into paid themes.
      3. There are already WAY too many themes. Why not make it easier for the less skilled web developer or the end user to create their own theme by pulling in functionality modules?
      4. My own review of themes over the years has proven frustrating. Searching by functionality yields either an unknown number or none too frequently. Many do not even specify functionality in the description, focusing on colors and other stuff that can already be seen. The description or keywords can’t be seen until clicking. In my opinion, the number of widgets, and how many are in areas other than the sidebar is the most important piece of information.
      5. Functionality should not be included in the customizer since the theme needs to be downloaded anyway. Just switch between themes to evaluate and get rid of that small piece of real estate that duplicates existing functionality or plug-ins and overrides desired CSS in many cases.
      6. A few more “most popular” themes of different varieties should be included so we hosts have the ability to capture that business.

      • Ulrich 9:48 pm on July 19, 2016 Permalink | Log in to Reply

        The theme review team is not really the correct place to discuss such a topic. It is also a very large topic.
        Let me still reply to a few of your points.
        2. We want to improve the search of themes and we have started to do so with the inclusion of new tags to filter by in WP 4.6
        3. There are a number of resources that people starting out can use like the underscores themes or they can reply on plugins for certain functionality.
        4. Some of this will be worked on with the new tags. We will discuss new tags in January. You should join the discussion then. This is also something the theme authors can work on.
        6. I know a number of hosts who include their own themes so it is possible. I am sure there is a way for you to automatically install themes on your clients installation.

        • madriverweb 6:59 pm on July 20, 2016 Permalink | Log in to Reply

          Thank you for the reply, some good points. I will research #3 and 6 in more detail. I knew this was not the best place to post this, but don’t know where is more appropriate for anyone to listen. Again, I can’t stress enough how easy it is to lose clients and prospects to more “friendly” platforms. So I figure the more places I say it, it might get back to those at WordPress who can do something about it. We recently had Chris Christoff from WordPress Core at our Burlington VT WordPress meetup group. When I asked for what audience WordPress.org and themes were being designed, he responded the person with the least computer skills, newbie. If we are losing people because other platforms offer a reasonable number of prettier standard themes and drag and drop functionality, we either need to make a related change or start marketing to a slightly more savvy audience.

          • Ulrich 7:43 am on July 21, 2016 Permalink | Log in to Reply

            Up to today Matt has been the person who has chosen the default themes. Twenty Sixteen was not included by default in the installation and needed to downloaded separately.

            I have not used any of the other services so it is difficult to get a full idea of the flexibility that they offer. There are a large number of page builder plugins out there.

            I like some of the default themes for their simplicity. By reducing the number of options make this situation less overwhelming. Are the newbie users able to make the correct decisions even when they don’t have the experience and knowledge.

            One place where WordPress excels is when a site has been set up it quite easy for users to use to publish their content.

      • Ulrich 9:41 am on July 23, 2016 Permalink | Log in to Reply

    • madriverweb 10:41 pm on July 25, 2016 Permalink | Log in to Reply

      Thanks, very interesting. I will follow that post and connect with her.

  • Ulrich 7:30 pm on July 12, 2016 Permalink |  

    Meeting notes for 2016 July 12 

    We had a great dicusssion where we discussed the action plan and the timeline for it and looked at a few items that needed a descision for the theme check sniffs. Read the meeting transcript in the Slack archives. (A Slack account is required)

    Structure

    Lead @karmatosed

    • update the handbook with make.blog posting guidelines.
    • Give the key reviewers the access
    • Update the about page accordingly
    • Get key reviewers access to edit the theme trac tickets

    Future Project

    Lead : @grapplerulrich

    • Create a new page for current, future and possible projects
    • List current and future projects
    • Enable comments to collect ideas

    Changing the review flow

    Lead : @karmatosed

    • Create a flowchart of the review process – Deadline 2 weeks
    • Remove reviewer if there is no response within 24 hours. Intially this will be manuall will plan to automate this in the future.
    • @emiluzelac updated the handbook to represent this

    Review baseline

    • Themes that do not fullfill the review baseline will be closed. The ticket will be closed if the theme has more then 3 prefixing or security issues. This also applies to the admin review queue.
    • It is not the end when a ticket is closed. The discussion can still continue and an update can always be updated.

    A sample text that you can use

    Reviewers are now allowed to close the ticket if 3 or more security or prefixing issues are found.
    This theme is being closed because the following security/prefixing issues have been found :

    Please do not get discouraged by the ticket being closed. If you have questions you can ask them here or in the #themereview channel on Slack. Fix these issues and ensure you have checked your theme for additional security or prefixing problems.

    You can read up more on security and prefixing on our resources page: https://make.wordpress.org/themes/handbook/review/resources/

    Also take this opportunity to carefully review your theme against theme requirements listed in the reference below.

    Once the issues are fixed upload the new version and we will review it again. https://wordpress.org/themes/getting-started/

    Theme Check Sniff

    The following items were voted on to include in the theme check

     
  • Ulrich 11:36 am on July 12, 2016 Permalink |  

    Agenda for 2016 July 12 

    The Theme Review Team holds a meeting weekly and we encourage all members to attend.

    Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

    Topic : Theme Review Team action plan

    We recently published the Theme Review Team action plan which we discussed partially in the last meeting.

    This time we will be discussing the timeline for the

    • Whole action plan, including line by line the action plan. Lets get a ticket, timeline or action for each bit.
    • Theme Check update

    I have an initial update on the Theme Check update. We have made a fork of the WPCS to the WPTRT GitHub repo. This will allow us to manage all of the checks as separate issues. You can help in a few ways:

    • Open a issue for all of the checks that we have mentioned in the WPCS issue 578.Please use the standard format.
    • Once an issue is opened we could use pull requests for unit tests. These allow us to be sure that our sniffs are working correctly. The test is normally a `inc` file that contains PHP code with a comment at the end to mention if it is bad or good. The test PHP file then list the lines where the should be an error.
    • Once a test is created a sniff can be built upon that.

    We already have a few issues open and a few of them need input from us. The first four are quite easy and I personally would give the go ahead.

    The following issues needs feedback. Please give feedback in the issue.

    The meetings typically last 30 minutes. If time permits, additional topics may be discussed.

    If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Skip to toolbar