This week we had 79 active reviewers Great…

This week we had 79 active reviewers! Great job everybody and thank you so much for contributing to reviewing themes! Even one theme a week can make a difference! Take the time and thank the following people when you can!

@AbdulWahab610, @Alobaidi, @Bipin-Singh, @Blair-jersyer, @DenUsenko, @Kenshino, @KostasNi, @Otto42, @Pixeldrops, @WEN-Solutions, @WPDevHQ, @anoopranawat, @ashiquzzaman, @benfurfie, @benlumia007, @bravokeyl, @burhandodhy, @catchthemes, @codeger, @cristian.raiber, @cristiano.zanca, @cryptex_vinci, @davide_entratici, @djrmom, @drshorifulbd, @edmund.turbin, @electricwp, @elschnuppero, @exactfare, @fashblogger, @george.grigorita, @greenshady, @hardeepasrani, @hazephase, @imon-Hasan, @imranaliweb, @ishulev, @itwfine, @jagirbahesh, @jimcee, @joedolson, @juhise, @kafleg, @kevinhaig, @khaerulamin, @kharisblank, @krishan123, @lyrathemes, @markmill2015, @mercime, @mikeselander, @monikarao, @nicola.bavaro, @octavianus, @peysso, @phillip.nunes, @prakashchhetri, @priyanshu.mittal, @protravelblogs, @psdtohtmlguru, @ptasker, @rabmalin, @rinkuyadav999, @rmdiaconu, @robciucioan, @robertacausin, @rodicaelena, @siobhyb, @smartcat, @softer, @spanchoo, @sunielk, @sushil-adhikari, @suvanno, @swadeshswain, @swetashrestha, @tadaimushi, @tinkerbelly, @yadimul29610

Weekly meeting agenda Our weekly meeting is on…

Weekly meeting agenda

Our weekly meeting is on Tuesday at 18:00 UTC in #themereview. What shall we talk about?

It’s good to every now and then have an open meeting so we can talk about anything that people want to. Lets do that this week. There is no set agenda so please add what you’d like to talk about in the comments.

Proposal: Better front page previews

The front page shown in the theme previewer has been a subject of much debate. There’s some movement on getting better demo content, but the front page is the first impression. We want it to look good and best represent what our themes are capable of.

Given the prevalence of non-blog themes, there needs to be a bit of balance here. I’ve thought long and hard about what the best route would be for handling this. The following is my proposal. I’d like to get all of your feedback as well as check in with @otto42 on the feasibility of it before creating a ticket.

Let me know your thoughts.

How the front page should be shown

I wanted to keep this simple and make sure that it works with both regular blog themes and themes that have a custom front-page.php.

The previewer should have some code that checks:

  • If front-page.php exists, override front page setting to show a page.
  • Else, show regular blog posts.

The idea in code

Note: This is potential code for the previewer to better describe my idea. It’s not something to put in your themes.

The following bit of code is a rough draft of how I think a feature should work.


add_filter( 'pre_option_show_on_front', 'wptrt_show_on_front' );
add_filter( 'pre_option_page_on_front', 'wptrt_page_on_front' );

function wptrt_show_on_front( $show ) {

	return wptrt_has_front_page() ? 'page' : $show;

function wptrt_page_on_front( $page ) {

	// 100 is the page ID to show.
	return wptrt_has_front_page() ? 100 : $page;

function wptrt_has_front_page() {

	// Need a check to see if the current theme being previewed 
	// has a front-page.php template. If it does, return TRUE.
	// Else, return FALSE.

	return false;

Theme Translations on

tl;dr: Theme translations and language packs are coming to and they’re awesome.

Howdy all you wonderful themers and theme reviewers,

The meta team has been working hard to enable theme and plugin translations on For themes, we plan on importing all active themes into – that is, any theme updated within the last two years. We expect to import them in the next few days or weeks, at most. This will involve importing ~1500 themes, which, combined, have about 315,000 total strings. After duplicates, the number drops to only 80,000 unique strings.

Below are some things you might want to know.

Why do I want managing translations for my theme? provides translations in dozens of languages and is ever expanding as new contributors join. (There are currently 140 locales on, but not all are active.) While you may have translated your theme into a few languages (or none!), there are likely more translators on in more languages.

But that’s not all! Themes in the directory will be able to take advantage of language packs! That means smaller download sizes for users, because themes will no longer need to ship translations. Eventually, we also plan to give priority to localized themes in localized directories; e.g., someone searching the Romanian theme directory will see Romanian themes prioritized over English-only themes.

What if my theme already ships translations?

Translations that are already shipped in themes will be initially imported into Again: we’ll import the strings and the translations on the initial import. We won’t continue to do that because the end goal would be for theme authors to remove the translations from their download, allowing language packs to fill the void.

What if I don’t want to use to manage translations for my theme?

Then you don’t have to! Translations shipped in a theme take precedence to language packs. If you continue to ship translations with your theme, WordPress will ignore the language packs. However, if a translation is available in a language your theme doesn’t support, WordPress will use the language pack for that language.

How do I add support for translations and language packs?

@Otto42 wrote up a great post on the topic back in 2013. (Wow, it’s been a long time!) There’s also a great page in the theme developer handbook which walks through how to internationalize your theme.

To fully support language packs, you’ll want to remove translations from your theme in your next update.

What if I want my translators to approve translations on

We’ve written up a plan for working with the polyglots team to enable this. There will be some initial pain in adding new, project-specific (aka theme-specific) translation editors, but afterwards your translators will join a growing group of WordPress translators and help make the entire ecosystem better.

Other questions?

Just ask! We’ll watch this thread and answer any questions you might have.


Theme review team weekly meeting notes The logs…

Theme review team weekly meeting notes

The logs are here:

Points from meeting:

1. Directory survey:

  • We should reconsider our keywords in our roadmap. Can we automate them? Can we have people able to update them?
  • We need to do a survey just on tags.
  • We began talking about how we should improve the admin interface for those with themes on org. The UI needs to be more friendly. How can they manage their entire theme?

Actionables: @greenshady to think about tags and with me come up with survey suggestion. @grapplerulrich: to get an easy cull list of tags. Add to roadmap: tag survey, redoing tags, theme admin on org.

2. Review survey:

  • Documentation is an issue. Could this be a language issue?
  • We talked about setting expectations for review time. This could be added to the uploader intro we are going to think about adding licenses to.
  • Would partial reviews be a solution, or do they cause more issues and create a bad experience?
  • Auto approving updates can speed up queues.
  • More we automate the better our queues.

Actionables: @grappleulrich is moving the button to help with abandoned. v2 of the workflow will be put as post before our planning meeting on July 7th.

3. Using themes survey:

  • We should consider in our roadmap the preview.
  • @otto42 is working on the preview and we should support what he is doing. This will bring the customizer to the front end securely. The user can then change things.