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 Guidelines, 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 are also weekly mentor meeting hours every Thursday at 18:00 UTC in #themereview

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • Jose Castaneda 9:26 pm on March 31, 2015 Permalink |  

    Handbook Examples: Stylesheets and Scripts 

    Let us continue with making some examples, shall we?

    This one will focus on scripts and stylesheets.

    No hard coding of scripts, styles and Favicons unless a browser workaround script. Everything should be enqueued.

    This does include the main stylesheet. I’ll start with a few:

    Example:

    All stylesheets must be enqueued.

    add_action( 'wp_enqueue_scripts', 'my_parent_theme_css' );
    function my_parent_theme_css() {
        wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
        wp_enqueue_style( 'child-style', get_stylesheet_uri(), array( 'parent-style' ) );
    }
    

    Example:

    No hard-coding of scripts.

    <script type="text/javascript" src="<?php echo get_template_directory_uri(); ?>/js/theme-slider.js"></script>
    <script>
    jQuery( document ).ready( function( $ ){
        $( '.slider' ).fancySlider({
            'autoplay': true,
            'navStyle': 'circles',
            });
    });
    </script>
    

    In the functions file:

    add_action( 'wp_enqueue_scripts', 'my_theme_slider_options' );
    function my_theme_slider_options(){
        wp_enqueue_script( 'theme-slider', get_template_directory_uri() . '/js/theme-slider.js', array( 'jquery' ) );
        wp_enqueue_script( 'theme-slider-init', get_template_directory_uri() . '/js/init.js', array( 'jquery', 'theme-slider' ) );
        // get user options
        $options = array();
        $options['autoplay'] = get_theme_mod( 'slider-autoplay', true );
        $options['navigation_style'] = get_theme_mod( 'numbers', 'circles' );
        
        wp_localize_script( 'theme-slider-init', 'themeSliderOptions', $options );
    }
    

    In the JavaScript file:

    jQuery( document ).ready( function( $ ){
        $( '.slider' ).fancySlider({
            'autoplay': themeSliderOptions.autoplay,
            'navStyle': themeSliderOptions.navigation_style,
            });
    });
    

    So, let’s share more examples and fill that handbook!

     
    • Frumph 10:27 pm on March 31, 2015 Permalink | Log in to Reply

      There’s a reason for hardcoded stylesheet’s to be placed first (ref: get_stylesheet_uri() – because you cannot specify placement in the enqueue’ing of scripts and CSS is a top down execution order interpreter. Without the ability to properly specify what comes first then you will never know if one thing is going to override the other.

  • Tammie 7:19 pm on March 30, 2015 Permalink |  

    Weekly meeting agenda

    This week we’ve got our usual weekly meeting. I’d like to talk about mentoring in the meeting. Why it’s important and how can we make it so more of you join us mentoring?

     
    • Aaron Jorbin 4:00 pm on March 31, 2015 Permalink | Log in to Reply

      I think the decision to only require .screen-reader-text if a theme has the accessibility-ready tag should be revisited. [31388] makes the default output of comments_popup_link include this class. As this is now a core outputted class, having it be REQUIRED makes sense to me since we already require a number of WordPress-generated CSS classes be styled.

  • Tammie 6:04 pm on March 26, 2015 Permalink |  

    Theme review team weekly notes

    The logs are here:
    https://wordpress.slack.com/archives/themereview/p1427220029004057

    We talked about when a plugin should or shouldn’t use TGM. It should at least relate to the theme. But as usual, when in doubt cc one of the admins or ask someone in #themereview.

    @grapplerulrich is going to get the recommended tags up in the handbook – woohoo!

    WordCamp London happened and was a great success, join me in saying hi to all the new theme reviewers from the weekend. You are all amazing! I’ve tried to find you all, but if I missed anyone out please shout out in the comments. Looking at the assignment button (some others may get picked up) for Friday a big hello to:
    @carol-hayes, @BinaryMoon, @aloisia, @designituk
    A big thanks to all the existing reviewers that turned up and those that helped mentor the 26+ people in the room.
    @wcorner is going to spearhead a new incentive to make the handbooks English language make more sense. This will be covering all aspects of the handbook. I’m really excited as this means we get someone to review it and improve what we already do!

    If you’ve got a contribution day with theme reviews coming up just let me know and we can make sure to give it a shout out.

     
  • Tammie 3:48 pm on March 24, 2015 Permalink |  

    This week’s meeting will be at 18:00 UTC today. Let us know if you’ve got a topic you’d like covered.

     
    • Maria Antonietta Perna 3:56 pm on March 24, 2015 Permalink | Log in to Reply

      One topic I’ve got a couple of questions about is about the 7 days deadline, but perhaps it’s not suitable for a meeting, just a simple reply by the admins: is the deadline automatically enforced or is the reviewer supposed to close the ticket if it’s gone unanswered for too long by an author by closing the ticket? Do tickets left open for more than 7 days have an impact on queues? Thanks!

      • Tammie 3:57 pm on March 24, 2015 Permalink | Log in to Reply

        Reviewers should never close tickets, but you can notify admins.

        • Maria Antonietta Perna 2:53 pm on March 25, 2015 Permalink | Log in to Reply

          Hi Tammie,
          Thanks for your reply. I guess I can notify you. The ticket number is 23160 and it’s gone unanswered for weeks now. The author must know about the 7-day policy because he/she is not new to submitting themes to the WP.org repo. On the other hand, if the author decides to reply during a time when I won’t be able to follow up on my review, there will likely be one more orphaned ticket for the team, which wouldn’t be all that nice.

        • Arya Prakasa 6:19 pm on March 26, 2015 Permalink | Log in to Reply

          Whoops … I did that twice without notify admins 😦

  • Tammie 3:56 pm on March 18, 2015 Permalink |  

    Join me in welcoming new key reviewers

    We all appreciate the great work everyone does with reviews. The admin team would like to today call out a few people specifically and say thanks by making them key reviewers.

    The role of key reviewer is given to people who have shown they consistently do amazing reviews. These are people who have proven over time they can be counted on as always delivering and have been consistent with their contributions.

    From the handbook:
    “People who are key reviewers are allowed to make themes live. These are an important piece to the theme review process, they make sure that the queues are kept low. In addition, you can guarantee they are a great source of reviewing knowledge as long standing reviewers.”

    We’d like to invite the following people to become Key Reviewers:

    Please join me in congratulating and welcoming these brilliant people to their new role.

     
  • Jose Castaneda 5:54 am on March 18, 2015 Permalink |  

    Handbook Examples: Language 

    Another round of examples, shall we? This one will focus on language examples.

    I’ll start it off:

    Required: load_theme_textdomain()

    add_action( 'after_setup_theme', 'my_theme_setup' );
    function my_theme_setup(){
        load_theme_textdomain( 'slug-text-domain', get_template_directory() . '/languages' );
    }
    // if child theme
    add_action( 'after_setup_theme', 'my_child_domain', 11 );
    function my_child_domain(){
        load_child_theme_textdomain( 'child-text-domain', get_stylesheet_directory() . '/languages'
    }
    
     
  • Emil Uzelac 3:43 am on March 18, 2015 Permalink |  

    Mobile-Friendly Themes 

    As some of you already know on April 21st, Google will expand use of mobile-friendliness as a ranking signal. This change will affect all mobile searches worldwide.

    Mobile-Friendly can be a Responsive design, but also an App that turns your theme into a “mobile version”.

    Since we don’t accept themes with mobile Apps because that would fall into a plugin-territory, our choice is Responsive and media queries instead of browser sniffing tools.

    Now, for the mobile-friendliness Responsive media queries will be enough and that is the very basic to be qualified as “mobile-friendly”.

    New algorithm will also take mobile usability into consideration when ranking sites.

    Please test your themes and make sure that we meet and exceed their expectations.

     
  • Ulrich 8:52 pm on March 17, 2015 Permalink |  

    Tracking tickets that need to reassigned 

    Recently we have had a number of tickets that have needed to be reassigned due to different reasons. The problem was is that these tickets are not easily identifiable as the ticket modified date changes once a comment is made in the ticket. I have created a new report so that we can publically track these tickets as a temporary solution till we find a better way. This report will help us to be more fair as the oldest ticket will be reassigned first. The tickets will be added/removed manually by an admin.

    Theme Reviewers: These tickets will be manually reassigned by an admin. Please just ask in Slack to be assigned a ticket.

    Theme Authors: If you are not getting a response from a theme author after 7 days please let us know in Slack and an admin will add your ticket to the report.

    The report can be found here: https://themes.trac.wordpress.org/report/30

    Let me know what you think of this solution. Are there any better ideas how we can track these reviews?

     
  • Tammie 3:18 pm on March 16, 2015 Permalink |  

    Agenda for this week’s meeting

    We’ve got a meeting at 18:00 UTC on Tuesday in Slack #themereview.
    Let us know what you’d like to talk about. So far we have:

    • Increasing the maximum size and requirement for screenshots. This is mainly changing documentation to keep up with what we already do.
    • Mentoring. We’ve briefly talked about it a bit last week, lets go into more depth this week.
     
  • Tammie 6:07 pm on March 11, 2015 Permalink |  

    Theme review meeting notes

    We met for our weekly meeting yesterday. The archive is here:
    https://wordpress.slack.com/archives/themereview/p1426010217001893

    Things talked about

    • We are going to make the request a ticket button a two step process to try and limit the spamming and issues we’ve had. We’re seeing this as a first step, we can do others after.
    • There was a lot of discussion around mentoring. Don’t forget every Thursday we have a mentorship session at 18:00 UTC.
     
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