[wp-meta] [Making WordPress.org] #7406: How might we allow larger theme authors to submit multiple themes for review at a time?

Making WordPress.org noreply at wordpress.org
Tue Jan 16 00:47:33 UTC 2024


#7406: How might we allow larger theme authors to submit multiple themes for
review at a time?
-----------------------------+---------------------
 Reporter:  iamtakashi       |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Theme Review     |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by dd32):

 Replying to [comment:6 acosmin]:
 > 1. Regarding the Latest Themes page on wp.org,

 I personally feel that this is for WordPress users benefit, not authors
 benefits, to the end-user it doesn't matter who the author is, only that
 it's a newer theme that might not be seen elsewhere.

 > Some authors really appreciate having visibility on that page, even if
 it's just for a few hours or a day.

 This is a real point, however, WordPress.org is not an advertisement
 platform nor Marketplace. Authors shouldn't be reliant upon this, and yes,
 I get it, the theme might get little view but I would argue that this is a
 bigger problem of discovery and filtering rather than anything else.

 > if we were to feature and set live five themes from a single author

 I was thinking there'd be a max of 2-3 per company in the queue, and that
 they'd naturally be approved not all at once (as they're not given
 preference) but rather as their time in the queue came up.

 > 2. Child themes. It seems like they might not be adding much value.

 This is a bigger problem around child themes and variations. For Block
 Themes I think variations work better than with the classic themes that
 kind of require child themes for the same functionality.

 Unfortunately simply saying something like "Why not just add a required
 minimum level of changes for a child theme" doesn't work, as those who
 would be affected would simply end up bulking out the child theme.

 One different suggestion would be that we consider a child theme of a
 theme by the same author not to be a "theme" but rather show it as a
 variation of the parent theme instead. That works for "simple" child
 themes, but not for larger child themes that take "Marketplace" and
 convert it to "Ticketing Office" (this is just an example, not a real
 situation that a theme would be suited for).

 > "I would probably suggest that the 2nd (and possibly 3rd?) submission
 should be at a lower-priority in the review queue than a new author
 though, out of fairness."
 >
 > If this can be implemented on trac, I'm all for it.

 The general way to do this is the `Priority` field, but we've used that
 for `new theme / theme update` (as that used to be the "priority for
 review" field).. Ideally we should've used a new field called `Type` for
 that I guess. But yeah, we could add a `Review Priority` field.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7406#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list