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.

There is also a second meeting temporarily on Thursday at 18:00 UTC in #themereview

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Justin Tadlock 6:57 pm on November 23, 2015 Permalink |  

    Trust and theme updates 

    In the past week or so, we’ve had to suspend a couple of themes from the directory. Suspending a theme is something that we never like to do. It’s usually more of a last resort type of thing. However, there are times when we need to take a firm stance.

    Recently, we started auto-approving all theme updates. Well, it’s not 100% automatic just yet. We’re still having to manually approve them in batches, but it’s a stepping stone to having this done automatically. In the future, we even want to make this a possibility for the initial theme submission process.

    The important thing right now is that we’re no longer doing reviews on theme updates.

    By doing this, we’re putting a lot of faith in theme authors. We’re betting that you all will continue following the guidelines. For the most part, this has been pretty dang successful.

    But, we’ve had to suspend two themes for adding in things that they were explicitly told to remove/change in their initial review. I imagine that there’s a few others we haven’t been notified about yet too.

    When this happens, it hurts everyone. It means that the more we see of things like this, the tougher it makes that decision to continue making things even more automatic.

    As a theme author myself, I want the TRT to continue putting more trust in theme authors. I don’t want this to be a place where we assume everyone is doing something wrong. I don’t want the team to play the role of gatekeepers to the directory. I don’t think that’s the future that any of us want.

    So, please take this as a friendly reminder to not re-add stuff in a theme update that you had to remove in the in initial review.

    • Ben Sibley 7:04 pm on November 23, 2015 Permalink | Log in to Reply

      The new update process has been amazing. It’s a shame that some people have abused the TRT’s trust, but as an author I have to say that I really appreciate the change.

    • Code Pixelz Market 7:09 pm on November 23, 2015 Permalink | Log in to Reply

      This is something good that made the queue speed up at least for updates. we shouldn’t break this up and fall back to manually getting things verified again. Theme developers will need to be more careful and true to self.

    • Shaped Pixels 7:13 pm on November 23, 2015 Permalink | Log in to Reply

      Sounds good and fair to me….I know the team has a lot to do and know things don’t happen overnight. It’s unfortunate that there are some who will abuse the trust because it affects everyone. Anyway, I’m looking forward to the new year as things progress.

    • Blair jersyer 8:38 pm on November 23, 2015 Permalink | Log in to Reply

      I’m not in good terms with automatic theme update approval. Since some guidelines may intentionaly being skipped (Restricting Core features, including more thant one link for editors ads). In most case, this will take down WP themes repository genuineness.

      an eye should be kept on changes anyway.

  • Jose Castaneda 1:18 pm on November 23, 2015 Permalink |  

    Meeting Agenda:

    No topic up for discussion at the moment. Have a topic you would like to bring up in our next meeting? Let us know in the comments.

    • Nilambar Sharma 4:43 am on November 24, 2015 Permalink | Log in to Reply

      It is great to see that abandoned tickets are getting some movement after they are brought to the New queue. But after that New queue is getting longer and longer. Can we do something to reduce it? How about pinging inactive reviewers for reviewing few tickets?
      Currently reviewers cannot take tickets from New queue themselves. It needs to be manually assigned by admin. May be if ticket status is changed to `new` or `reopened`, reviewers can assign ticket themselves [This is just my idea].
      Also queue push program could be done weekly for few weeks until queue is brought down to normal.

      • Code Pixelz Market 11:18 am on November 24, 2015 Permalink | Log in to Reply

        +1 to @Nilambar‘s suggestion of changing ticket status. As I wanted to clear themes from the queue but I had to ask on slack and you later assigned them to me. if I could take those myself, would have been faster and easier. :)

      • Jose Castaneda 5:55 pm on November 24, 2015 Permalink | Log in to Reply

        Yes, I was reached out by another that wanted to tackle that as well. I want to say it is a trac thing, so if you want to try, create a meta ticket for it. As far as I know, admins are not able to change the status of the ticket, just priority which isn’t what needs changing.

  • Jose Castaneda 10:49 pm on November 22, 2015 Permalink |  

    Update on doing_it_wrong theme 

    Hi! You may recall some time ago there was a post that mentioned a thing called the doing_it_wrong theme. Yeah. That small tool to help in looking for things when conducting a review. Or perhaps when you are trying to teach a group of people about theme reviews. Yes, that. If you haven’t already, check out the github repo: https://github.com/WPTRT/doingitwrong

    I’ll wait a second so you can check it out.

    grabs water and takes a sip

    Okay, now that you’ve looked over the theme a little let’s talk about what it all entails. A lot of the readme’s documentation was posted some time ago. Earlier today a small commit was made that added a few more things to the theme. Added were:

    • JS error
    • missing validation/sanitation of customizer setting
    • updated readme documentation
    • bypassing theme-check
    • custom comment listing

    The bigger hurdle here is education of customizer validation and sanitation. For some examples and ideas you can check out the sample library on github:

    For even more reading when it comes to creating safe themes read the guide Frank so awesomely wrote out:

    1. Introduction
    2. Validation
    3. Sanitation
    4. Securing Post meta
  • Jose Castaneda 6:44 pm on November 9, 2015 Permalink |  

    Meeting agenda: 2015/11/09 

    Our meeting tomorrow currently has no set agenda. If you would like to discuss something in particular, comment away. Or perhaps suggestions for the following weeks as we get closer to the Holiday season in some countries.

  • Emil Uzelac 11:07 pm on November 6, 2015 Permalink |  

    Creative Commons Licenses in the Theme Directory 

    This applies for themes too: Crossposting Creative Commons Licenses in the Plugin Directory

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc