15 Responses

  1. Ryan Hellyer
    Ryan Hellyer Published |

    The theme review system was broken for the beginning. I’m surprised you bothered reviewing any themes at all. I’ve been hoping it would all come tumbling down and be thrown out long before now. The current system was always going to be an enormous hog on volunteers time.

    Reply
    1. rajaguru83
      rajaguru83 Published |

      Yes. absolutely.

      Reply
  2. Joy
    Joy Published |

    Unleashing all that bad code into the repository will negate the vision stated for it : “not just any WordPress themes, but the best WordPress themes”. Other parts of the WordPress ecosystem rely on themes behaving a certain way (presentation not functionality, respecting user options, not storing content in theme options, not breaking plugins, defining standard classes, using the Customizer instead of a theme options page, being child theme ready, using core functions so filters and actions are called, and more).

    I don’t think “that” feeling is worth as much as having mostly good code in the repository. So it takes awhile. That’s really no big deal.

    Reply
    1. Ulrich
      Ulrich Published |

      “not just any WordPress themes, but the best WordPress themes”

      This is not written in stone. We need to be able to adapt and change to be able to improve.

      Themes that have not been updated in the last two years are not shown in the search. There are themes that were released in 2008 that are breaking most of the requirements. They are live on the site but are not getting many downloads.

      We can create the same effect for themes with issues.

      Reply
      1. Thiago Senna
        Thiago Senna Published |

        I don’t know if anyone have already said that, but hiding child-themes in search for not having updates is not cool, in my humble opinion. Usually Child themes do not need updates, so would be better to hide them only if the parent theme has not been updated.

      2. Joy
        Joy Published |

        A recent comment in Slack #pluginreview about version numbers made it clear that the plugin repository is NOT a development repository. “Submissions should be completed and ready to go plugins”

        The theme repository is the same. Letting any old theme get in, and then users having to rely of someone else trying it and giving it a star rating, makes it more like the rest of the web where there are no standards. By enforcing standards to get in the repository, it will have less development versions and more complete and ready to go versions.

  3. acosmin
    acosmin Published |

    Nothing more to say, I agree 100%. When can we start, do we need to vote?☺

    Reply
  4. Brandon
    Brandon Published |

    Improving the sniffs is great, but it might also be great to display a score or letter grade based on the overall results. This can be done with tools such as CodeClimate, Scrutinizer, CodeCov, etc. Many users rate and pick themes based on only the design, and having a clear grade/score could better help users determine how likely a theme might break with plugins, or cause issues with long-term maintainability. By having this prominent it may be one of the only ways users can find that 1 great theme out of the 100.

    Reply
    1. Ulrich
      Ulrich Published |

      I was thinking of something similar but allowing issues to be marked as false positives if need be. https://make.wordpress.org/themes/2017/03/27/chat-with-matt-about-the-future-of-theme-repo/#comment-42923

      Reply
  5. Ulrich
    Ulrich Published |

    Thank you for posting this. It really helps to have clear place where an opinion is written up when we can check back later instead of random comments in Slack. 🙂

    Reply
  6. Nicolas
    Nicolas Published |

    Great reading. Thanks for taking the time to share this vision. Considering your WP background, this is very interesting.

    It is totally consistent with the “let users decide” approach proposed by Matt in a recent WP tavern post : https://wptavern.com/zerif-lite-returns-to-wordpress-org-after-5-month-suspension-and-63-decline-in-revenue#comment-210935

    Now a personal feedback about featured themes. When I submitted the first version of my theme to the WordPress.org theme repo, it happened to be “staffed picked” in the featured list, because this was possible by this time.

    It turned out to be really appreciated by users, which is ultimately the goal of the theme repo, and has now 100K+ active installs. I consider my theme lucky and I wonder what would have happened with the current system. A realistic guess is that most of the users might not have had the possibility to discover it and install it on their website.

    I look forward to reading the part 2 🙂

    Reply
  7. Patrick
    Patrick Published |

    As a theme user not a theme maker I ‘d like to ask about one aspect.

    When a plugin gets updated we usually get to see a change log as part of the WP library but when an update to a theme arrives, even the “official” WP themes eg Twenty Twelve” etc dont indicate any kind of change log. While theme updates are an indication that a theme is still supported by its producers, and the exten tof that support can vary. I’m curious as to what the common reasons are for the necessity of a theme update.

    Some themes may be years old without updates and still “work” while others seem to get frequent updates.

    I realise there may be compatibility or security issues that arise and themes may be updated accordingly but we usually never know any particular reason, as theme update dialogues rarely in my experience link to a detailed change log, though I know of one paid for theme that did, but most free themes (unlike free plugins) do not.

    Reply
  8. Vashishtha Kapoor
    Vashishtha Kapoor Published |

    Hi Justin

    The fact that users are pretty quick to figure out the drawbacks and problems inside themes is very true. When someone submit theme for review on wordpress.org, it is mostly tested as to code plagiarism and then to security.

    But support for other plugin is much required. most of the times, developers forget to add some hooks so that plugins can add anything to the header or footer. and this is the big reason.

    Reply

Leave a Reply

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/Web site in attribution.

Please use your real name or a pseudonym (i.e., pen name, alias, nom de plume) when commenting. If you add your site name, company name, or something completely random, I'll likely change it to whatever I want.

css.php