Theme Review Team

Updates from Emil Uzelac Toggle Comment Threads | Keyboard Shortcuts

  • Emil Uzelac 8:39 pm on October 7, 2015 Permalink |  

    Automation here we come! 

    As a step towards automation we are going to approve all updates at least once a week. 

    If you guys have any questions, please don’t hesitate to post below!

  • Emil Uzelac 9:10 pm on September 25, 2015 Permalink |  

    comment_form changes in WordPress 4.4 

    Crossposting Changes to fields output by comment_form in WordPress 4.4

  • Emil Uzelac 3:49 am on September 14, 2015 Permalink |  

    Theme Review Team Needs Your Help! 

    If you are already a reviewer, please help us out with few tickets and if you are not, just click here and join our team.

    We really need to reduce these numbers to a lowest possible count.

    Large amount of assigned tickets are pretty much “ghosts” (reviewer auto-assigned by a button) and they are our first priority.

    Every little helps, thanks all!

    Current stats:

    • 314 new tickets are waiting for review.
      • 106 tickets are older than 4 weeks
      • 173 tickets are older than 2 weeks
      • 203 tickets are older than 1 week
      • 255 tickets are older than 3 days
    • 205 tickets are assigned.
      • 200 tickets are older than 4 weeks
      • 202 tickets are older than 2 weeks
      • 204 tickets are older than 1 week
      • 204 tickets are older than 3 days
    • 55 are approved but are waiting to be made live.

    Last 7 days:

    • 179 tickets were opened
    • 137 tickets were closed:
      • 123 tickets were made live.
        • 17 new Themes were made live.
        • 106 Theme updates were made live.
        • 11 more were approved but are waiting to be made live.
      • 13 tickets were not-approved.
      • 1 tickets were closed-newer-version-uploaded.
  • Emil Uzelac 9:06 pm on June 10, 2015 Permalink |  

    Theme Unit Test 

    Over a year ago I took the initiative to start a brand new theme unit test data. As many of you already know we are using the same one for years with no changes or notable improvements other than bug fixes.

    Back in January we ported the data over to our GitHub account and that was an excellent start.

    The question is: Does current TUT works, if not should we improve the existing one or start from scratch?

    • Tammie 9:11 pm on June 10, 2015 Permalink | Log in to Reply

      I think having it on Github is the right move. I also think starting from scratch is a bad idea and a distraction when we have a lot of other things going on. Never saying never, but would absolutely question doing it now.

      It works very well as a solid baseline. There isn’t a need now to complicate or throw it out. I would not like to see a new one now. Also, consider the process that it has to go through from GH. It takes a lot to get that file to release.

      • Emil Uzelac 9:28 pm on June 10, 2015 Permalink | Log in to Reply

        The main reason why I brought this here is to get few more voices involved, we have over 1,000 subscribers now. GitHub is great, but pretty isolated, at least TRT account is :)

        We should simplify and clean the overall data and make sure that everything is still current and works the way it should.

        Specifics: Menus, blockquotes, empty post/pages, images etc. vertical featured images?

        Take a look at http://ottodestruct.com/democontent/ isn’t that nice and clean?

        There’s plenty on our plate already and I fully understand that.

        • Tammie 9:57 pm on June 10, 2015 Permalink | Log in to Reply

          That’s not all new though. Maybe wording this not as brand new but as let’s work on existing one is better. I stand by we have to stay the to our roadmap and not tackle too much right now.

          • Emil Uzelac 10:46 pm on June 10, 2015 Permalink | Log in to Reply

            Either or works and it doesn’t have to be prioritized. Wording is accurate “brand new” was the initial idea we had before :)

      • Gary Jones 7:10 am on June 11, 2015 Permalink | Log in to Reply

        I agree that improving the existing file is better than starting from scratch.

        > It takes a lot to get that file to release.

        That is definitely part of the problem – there are tickets in Trac for bugs in the exporter related to this. The export is a simple XML file – and it should be able to be edited directly as such, without having to have a test site, import the unit test file, amend and re-export. If there was a push to fix the exporter bugs, then improving theme unit test file becomes considerably easier.

    • Edward Caissie 9:14 pm on June 10, 2015 Permalink | Log in to Reply

      Obviously there was a reason to bring forward this “question”, what do you see as being a problem with the current test data, aside from it being old? I’m thinking more to continue the discussion from that point before going back to the drawing board. It might even serve a greater good to get sample posts in from theme authors for things they add to their “base” test data as well.

    • Andre 9:56 pm on June 10, 2015 Permalink | Log in to Reply

      There’s been times I wish the TUT was redone to be more of a real world test; I was even planning to make my own at one point — using the TUT as a guideline of course. I’ve even seen things when testing my themes where a few quirky things within the content exists, for example, odd characters showing up in the content, a post title that is supposed to have a word in bold (doesn’t work and isn’t there)…there’s a few other things I noticed too, but don’t remember them at this moment. When I test my next theme out, I will make notes.

      However, I believe it’s a valid query of whether a new theme unit test data is needed, and I say yes. The question though is when and to what extent should the changes consist of.

    • Gary Jones 7:16 am on June 11, 2015 Permalink | Log in to Reply

      The open and closed issues and pull requests on https://github.com/manovotny/wptest (a fork from TUT) serve as a good start of the highlighting the problems with the TUT content.

  • 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.

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