Agenda for 2018 November 13

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

Channel: #themereview | Time: Tuesday, 13 November 2018, 18:00 UTC.

The following will be discussed during the meeting:

  • Add align-wide and block-styles tags (filters)
  • Talk about not allowing create_function(), issues with PHP v7.2+.
  • Talk about not allowing authors that promote non GPL products (via affiliate links) on their websites. (related)

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

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

October 23rd Theme Review Team Meeting Summary

Child Themes

The decision is that themes must have certain uniqueness to be allowed in the repository, voted 10 yea and 1 nay.

More details here.

Team Lead Selection

Unfortunately, there was no official decision about this topic.

Theme Readme

The decision is that themes will use the same readme.txt format as plugins.

More details here.

Removing the “Review a Theme” button

The button will be removed, voted 6 yea and 1 nay. To review a theme from now on, just show up in Slack, say hi, and ask for a theme to review. (Or go the Trac ticket and assign yourself as a reviewer. Preferably the oldest open one.)

Discuss the TwentyNineteen issue

Attendants agreed with the comments in the GitHub Pull Request.

GitHub Pull Request.

Wrap-up for on-boarding discussion

On-boarding will be allowed for few months, with some specific rules. Handbook will be updated with specifics.

More details here.


@acosmin, @andre-jutras, @azexo, @azexo, @benlumia007, @bothera, @conlaccento, @cristianozanca, @dannycooper, @dingdang, @dingo_bastard, @greenshady, @imranaliweb, @jcastaneda, @joyously, @kafleg, @kevinhaig, @lamarajan, @luehrsen, @marcio-zebedeu, @nikschavan, @otto42, @poena, @rabmalin, @santoshraut, @sharaz, @themeansar, @thinkupthemes, @williampatton, and Charlie Livingston.

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

New requirements

Following our meeting conversation, we have new requirements:

Child themes must include more than minor changes (such as font and colour changes) to the parent theme to be accepted. To make it easier on the reviewer, make sure you describe what modifications/features you did on top of the parent theme (in a ticket comment). – req – 

readme.txt – Use this format for your readme.txt file. New themes need to follow this rule as of October 25th, 2018. Old themes have a 6 months grace time from this date. – req –

Trusted Authors:

You can only upload one theme per week if you are a trusted author, no matter how many theme author accounts you are affiliated with. Doing otherwise or getting caught will result in a permanent ban from TA and all themes removed for all users involved.

Theme Review Team Meeting Agenda – 23rd October 2018

This week we have a few items on the agenda to chat about. These are open discussion items, let’s hear your thoughts about them.

  1. Child Themes – minimum requirements to constitute a viable change, submission limitations for them in the queue and for TA program.
  2. Team Lead Selection – let’s talk about how leads are chosen, how we can choose going forward and what benefits we can get from open selection.
  3. Theme Readme – can we standardise on a single Readme format for themes to use going forward? What do we want in this, what fields are already required, when should we start asking authors include the decided format?
  4. Removing the Review a Theme button. (@poena request)
  5. Discuss this Twentynineteen issue. (@poena request)
  6. Wrap-up for on-boarding discussion.

Discussion about allowing themes to use onboarding functionality

A few weeks ago, in a meeting, we were talking about allowing onboarding functionality and we had an interesting suggestion to make a guest post on the blog. Your opinions on this topic are welcomed.

Author: Themeisle

Discuss setup/onboarding wizard guidelines for themes

Hello! We would like to bring into discussion our approach for onboarding users for our one page theme, Neve, which is submitted for review here

We would like to know TRT’s opinion, and hopefully, through an open discussion with users and theme authors, find better ways of onboarding users, in every theme. Our solution is not perfect, but we think it’s a good starting point for this discussion.

The mechanism

Immediately after activating the theme, you are taken to the Setup Wizard where you are presented with some demos that you can preview or/and import with a single click. The wizard takes you through all the necessary steps to set up your site fast, from just one place!
The wizard is dismissable, so you can choose to use it, or just skip it.

Our reasons

1. Not all the themes are the same, and because of that, we feel that theme authors (same as plugin authors) should be able to guide their users towards the best UX path possible.
In the case of a One Page theme, there is no point in enabling latest posts as default, as 99% of the users actually want the One Page frontpage.
In the case of Neve, we have built a theme with multiple potential front-pages, this is how the theme is presented and what the users expect to get from it.

2. If this is a problem, we can make much clear/easier to understand in the onboarding that the user can keep the latest posts option, maybe add a “standard” site library that user can pick and be directed to the customizer for e.g, like “I want the default blog listing frontpage”. If we auto-start without this option, we agree it might get a bit confusing.

3. WooCommerce is already doing this and we think they have a good reason for it ( or they don’t know what’s best for their users ).
Allowing theme authors to do this, would allow us to do lots of things for an improved UX, guide users with not only the demos sites but maybe with the style, fonts, plugins and much more. Sure, we would first need to agree that WordPress core hasn’t adapted to new WordPress uses, otherwise this should have been already there, but at least as plugin authors can, we think we should leave theme authors deliver the best UX for each particular theme.

4. We found out that 99% of the existing Neve sites use the demo provided in the onboarding. We think this is a good indicator of what the users actually want, and think that requiring 99% of the users to take an extra step to set up their site, only so that the remaining 1% don’t have to take an extra step of skipping the onboarding is not in the best interest of the user.