Making WordPress.org: Ticket #1515: Adding more info in the email sent after theme is submittedhttp://meta.trac.wordpress.org/ticket/1515
<p>
When theme is submitted, email is sent which contains minimal information. We can add some additional info so that it could help author himself/herself can check their theme against the guideline. May be it will help making theme approval faster.
</p>
<ul><li>Theme review guideline link long with review process
</li><li>Encourage to contribute by reviewing
</li></ul><p>
Currently it is like
</p>
<pre class="wiki">Thank you for uploading THEME_NAME to the WordPress Theme Directory. If your theme is selected to be part of the directory we'll send a follow up email.
Feedback will be provided at TICKET_LINK
</pre>en-usMaking WordPress.orghttp://meta.trac.wordpress.org/chrome/site/your_project_logo.pnghttp://meta.trac.wordpress.org/ticket/1515
Trac 1.2.2slackbotWed, 13 Jan 2016 10:51:11 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:1
http://meta.trac.wordpress.org/ticket/1515#comment:1
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1452682268006391"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketrabmalinMon, 18 Jan 2016 07:36:38 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:2
http://meta.trac.wordpress.org/ticket/1515#comment:2
<p>
I have written some points that could be added in the message. Pardon me for mistakes in language. (Confession of non-English :D )
</p>
<pre class="wiki">&lt;h2&gt;Review process&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
Want to know about Theme Review Process? See this &lt;a href="https://make.wordpress.org/themes/handbook/review/"&gt;link&lt;/a&gt;.
&lt;/li&gt;
&lt;li&gt;You theme will be reviewed against &lt;a href="https://make.wordpress.org/themes/handbook/review/required/"&gt;Theme Review Guideline&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Required points should be resolved to make theme approved. &lt;a href="https://make.wordpress.org/themes/handbook/review/recommended/"&gt;Recommended&lt;/a&gt; points includes best practices in WordPress theme development and theme will not be rejected on the base of Recommended.&lt;/li&gt;
&lt;li&gt;Your theme will have to wait for your turn for review. You can check this &lt;a href="https://themes.trac.wordpress.org/report/2"&gt;link&lt;/a&gt; to find out your theme's position in the queue. &lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Reviewer is assigned to your theme&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Reviewer will post comment in the ticket. You would to fix those issues and re-upload your theme. You should re-upload your theme from &lt;a href="https://wordpress.org/themes/getting-started/"&gt;here&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;This step will iterate until all issues have been fixed.&lt;/li&gt;
&lt;li&gt;You should re-upload your theme within 7 days. If there is no response for 7 days, ticket will be closed as not-approved. If you need more time to update then you should mention it in the ticket.&lt;/li&gt;
&lt;li&gt;If there is no review comments by reviewer for more thatn 7 days, you can ask admin in Slack for putting back your theme in NEW queue. See this &lt;a href="https://make.wordpress.org/chat/"&gt;link&lt;/a&gt; to register in Slack. Channel is &lt;strong&gt;#themereview&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Your theme is approved&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;After reviewer completes the review and approve your theme, admin will again review it. Only after admin approval your theme will be live. You can check this &lt;a href="https://themes.trac.wordpress.org/report/24"&gt;link&lt;/a&gt; to find out your theme position in the approved queue.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;You want to be a theme reviewer?&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Great. The team is open to anyone and you can easily get started. &lt;a href="https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/"&gt;Become a reviewer&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</pre>
TicketslackbotMon, 18 Jan 2016 07:40:08 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:3
http://meta.trac.wordpress.org/ticket/1515#comment:3
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1453102805006531"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketslackbotTue, 19 Jan 2016 18:35:53 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:4
http://meta.trac.wordpress.org/ticket/1515#comment:4
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1453228551006797"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketslackbotSat, 14 May 2016 11:28:04 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:5
http://meta.trac.wordpress.org/ticket/1515#comment:5
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1463225283003652"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketslackbotTue, 07 Jun 2016 18:16:05 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:6
http://meta.trac.wordpress.org/ticket/1515#comment:6
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by poena. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1465323363000242"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketkkoppenhaverTue, 07 Jun 2016 19:20:55 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:7
http://meta.trac.wordpress.org/ticket/1515#comment:7
<p>
Here's my pass at it. Used much of @rabmalin's original content, but also added some. Feedback welcome.
</p>
<p>
<br />
</p>
<h2 id="TheWordPressThemeReviewProcess">The WordPress Theme Review Process</h2>
<p>
If you want to know about Theme Review Process in detail, <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/"><span class="icon">​</span>see this link</a>
</p>
<h2 id="ThemeReviewQueue">Theme Review Queue</h2>
<p>
Your theme is now in the Theme Review queue waiting to be reviewed by a member of the <a class="ext-link" href="https://make.wordpress.org/themes/"><span class="icon">​</span>Theme Review Team</a>. You can check your status in the queue at any time by following <a class="ext-link" href="https://themes.trac.wordpress.org/report/2"><span class="icon">​</span>this link</a>.
</p>
<h2 id="YourThemeGetsaReviewer">Your Theme Gets a Reviewer</h2>
<p>
Once your theme gets to the top of the queue, it will be assigned to the next available reviewer. This reviewer will ensure that your theme is ready to go into the Wordpress.org theme repository. Your theme will be checked against the Theme Review Guidelines and at the very least, your theme will need to satisfy all the <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/required/"><span class="icon">​</span>required theme checks</a>.
</p>
<p>
In addition, there are also <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/recommended/"><span class="icon">​</span>recommend points</a> that include best practices in WordPress theme development. Your theme will not be rejected if it does not meet all of these requirements, but they do represent best practices that should be followed if possible.
</p>
<p>
Once a reviewer has had a chance to take a look at your theme, they will post a comment on the ticket indicating any changes that need to be made based on their review. For the review to move forward, you will need to fix those issues and <a class="ext-link" href="https://wordpress.org/themes/getting-started/"><span class="icon">​</span>re-upload your theme</a>. You will continue collaborating with the reviewer in this way until all issues are resolved.
</p>
<p>
Once you are assigned a reviewer, it's important to stay active on the ticket. If the reviewer does not hear from you within 7 days, the ticket will be closed as not-approved. If you need more time to make updates, you should let the reviewer know on the ticket.
</p>
<p>
Likewise, if you don't hear from the reviewer for more than 7 days, you can ask an admin in Slack to put your theme back into the queue. See <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>this link</a> to register in Slack and make a post in the <strong>#themereview</strong> channel.
</p>
<h2 id="YourThemeisApproved">Your Theme is Approved</h2>
<p>
When the reviewer approves your theme, it will be sent to an admin for final review. You can view your position in the admin queue <a class="ext-link" href="https://themes.trac.wordpress.org/report/24"><span class="icon">​</span>here</a>. After approval by an admin, your theme will then be allowed in the Wordpress.org theme repository.
</p>
<h2 id="WanttoGetInvolved">Want to Get Involved?</h2>
<p>
We frequently get asked <strong>"Why does it take 3 to 6 months to get a theme approved?"</strong> The simple answer is that there are many more themes submitted than there are reviewers to review them. You can help to reduce this time by making sure you review all the required and recommended checks before submitting your theme. In addition, if you want to become a reviewer, the Theme Review Team is open to anyone and you can <a class="ext-link" href="https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/"><span class="icon">​</span>easily get started</a>.
</p>
<h2 id="Questions">Questions?</h2>
<p>
If you have questions throughout the review process, you can ask the reviewer on the ticket or join us in Slack and ask in the <strong>#themereview</strong> channel.
</p>
<p>
Thanks,
The WordPress Theme Review Team
</p>
TicketgrapplerulrichTue, 07 Jun 2016 20:36:09 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:8
http://meta.trac.wordpress.org/ticket/1515#comment:8
<p>
@kkoppenhaver - Thank you for the next version. A few points of feedback
</p>
<ul><li>I find the text too long. We need to make it shorter. We can link to another page which explains the process in more detail.
</li><li>It would be better to replace "see this link", "this link" &amp; "here" with a better title. e.g. "Theme Review Process", "review queue", "join the WordPress Slack" &amp; "admin queue"
</li><li>If we write wordpress.org it is either all small or with capital W &amp; P
</li><li>I would replace "3 to 6 months" with "x time" or even change the paragraph to make it shorter:
<blockquote class="citation">
<p>
The theme reviews are done by volunteers. You can help speed up the process by joining the Theme Review Team and doing reviews yourself.
</p>
</blockquote>
</li></ul>
TicketkkoppenhaverTue, 07 Jun 2016 20:50:00 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:9
http://meta.trac.wordpress.org/ticket/1515#comment:9
<p>
Good points. Revised below.
</p>
<p>
<br />
</p>
<h2 id="TheWordPressThemeReviewProcess">The WordPress Theme Review Process</h2>
<p>
If you want to know about Theme Review Process in detail, see the <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/"><span class="icon">​</span>Theme Review Handbook</a>
</p>
<h2 id="ThemeReviewQueue">Theme Review Queue</h2>
<p>
Your theme is now in the Theme Review queue waiting to be reviewed by a member of the <a class="ext-link" href="https://make.wordpress.org/themes/"><span class="icon">​</span>Theme Review Team</a>. You can <a class="ext-link" href="https://themes.trac.wordpress.org/report/2"><span class="icon">​</span>check your status</a> in the queue at any time..
</p>
<h2 id="YourThemeGetsaReviewer">Your Theme Gets a Reviewer</h2>
<p>
Once your theme gets to the top of the queue, it will be assigned to the next available reviewer. Your theme will be checked against the Theme Review Guidelines and at the very least, your theme will need to satisfy all the <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/required/"><span class="icon">​</span>required theme checks</a>.
</p>
<p>
Throughout the process, reviewers will post comments on the ticket indicating changes that need to be made. You will need to fix those issues and <a class="ext-link" href="https://wordpress.org/themes/getting-started/"><span class="icon">​</span>re-upload your theme</a>. You and the reviewer will collaborate in this way until all issues are resolved.
</p>
<p>
Once your theme is being reviewed, it's important to stay active on the ticket. If you need more than 7 days to make updates, you should let the reviewer know on the ticket, otherwise the ticket will be closed as not-approved.
</p>
<h2 id="YourThemeisApproved">Your Theme is Approved</h2>
<p>
When the reviewer approves your theme, it will be sent to an admin for final review. You can <a class="ext-link" href="https://themes.trac.wordpress.org/report/24"><span class="icon">​</span>view your position in the admin queue</a> at any time. After approval by an admin, your theme will then be allowed in the WordPress.org theme repository.
</p>
<h2 id="WanttoGetInvolved">Want to Get Involved?</h2>
<p>
Theme reviews are done by volunteers. You can help speed up the process by <a class="ext-link" href="https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/"><span class="icon">​</span>joining the Theme Review Team</a> and doing some reviews yourself.
</p>
<h2 id="Questions">Questions?</h2>
<p>
If you have questions throughout the review process, you can ask the reviewer on the ticket or join us in Slack and ask in the <strong>#themereview</strong> channel.
</p>
<p>
Thanks,
The WordPress Theme Review Team
</p>
TicketpoenaWed, 08 Jun 2016 15:57:41 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:10
http://meta.trac.wordpress.org/ticket/1515#comment:10
<p>
I’m sorry if I sound negative, but I feel that authors are required to read the guidelines before submitting a theme.
The first part of the text makes it sound like reading the guidelines is optional.
</p>
<hr />
<p>
Thank you for uploading THEME_NAME to the WordPress Theme Directory.
</p>
<p>
<strong>The WordPress Theme Review Process</strong>
Your theme is now in the Theme Review queue. You can <a class="ext-link" href="https://themes.trac.wordpress.org/report/2"><span class="icon">​</span>check your status</a> in the queue at any time.
Once your theme reaches the top of the queue, it will be assigned to the next available reviewer.
You will be notified by e-mail when the review starts.
</p>
<p>
Your theme will be checked against <a class="ext-link" href="https://make.wordpress.org/themes/handbook/review/"><span class="icon">​</span>the Theme Review Guidelines</a> and it needs to pass all the requirements to be included in the Theme Directory.
Throughout the process, the reviewer will post comments on the ticket indicating changes that needs to be made. You will need to fix those issues and <a class="ext-link" href="https://wordpress.org/themes/getting-started/"><span class="icon">​</span>re-upload your theme via the upload page</a>. You and the reviewer will collaborate in this way until all issues are resolved.
</p>
<p>
During the review, it's important to stay active in the ticket. If you need more than 7 days to make updates, you should let the reviewer know, otherwise the ticket may be closed as not-approved.
</p>
<p>
When the reviewer approves your theme, it will be sent to an admin for a final review.
You can also <a class="ext-link" href="https://themes.trac.wordpress.org/report/24"><span class="icon">​</span>view your position in the admin queue</a>.
After approval by an admin, your theme will be published in the WordPress.org Theme Directory.
</p>
<p>
<strong>Want to Get Involved?</strong>
Theme reviews are done by volunteers. You can help speed up the process by <a class="ext-link" href="https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/"><span class="icon">​</span>joining the Theme Review Team</a>.
</p>
<p>
<strong>Questions?</strong>
If you have questions you can ask the reviewer in the ticket or <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>join us on Slack</a> and ask in the #themereview channel.
</p>
<p>
Thanks,
The WordPress Theme Review Team
</p>
TicketkkoppenhaverWed, 08 Jun 2016 16:19:32 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:11
http://meta.trac.wordpress.org/ticket/1515#comment:11
<p>
Looks good to me. I like how you tightened up the copy a bit and removed that ambiguity.
</p>
TicketrabmalinThu, 23 Jun 2016 05:59:42 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:12
http://meta.trac.wordpress.org/ticket/1515#comment:12
<p>
It seems current mail format is <code>text/plain</code>. But our new content should support some HTML. Or would it worth changing mail format for this single email? <a class="ext-link" href="https://developer.wordpress.org/reference/hooks/wp_mail_content_type/#comment-777"><span class="icon">​</span>https://developer.wordpress.org/reference/hooks/wp_mail_content_type/#comment-777</a>
</p>
Ticketdd32Thu, 14 Jul 2016 05:38:00 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:13
http://meta.trac.wordpress.org/ticket/1515#comment:13
<p>
Replying to <a class="ticket" href="http://meta.trac.wordpress.org/ticket/1515#comment:12" title="Comment 12">rabmalin</a>:
</p>
<blockquote class="citation">
<p>
It seems current mail format is <code>text/plain</code>. But our new content should support some HTML. Or would it worth changing mail format for this single email? <a class="ext-link" href="https://developer.wordpress.org/reference/hooks/wp_mail_content_type/#comment-777"><span class="icon">​</span>https://developer.wordpress.org/reference/hooks/wp_mail_content_type/#comment-777</a>
</p>
</blockquote>
<p>
You should really have a <code>text/plain</code> fallback with any <code>text/html</code> email (although not everyone does). Until WordPress supports nicer HTML emails, perhaps you can reword it not to use <code>&lt;a href&gt;</code> links and instead just use inline links?
</p>
TicketrabmalinSat, 16 Jul 2016 04:08:48 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:14
http://meta.trac.wordpress.org/ticket/1515#comment:14
<p>
@poena up for rewording and keeping inline links only? :-)
</p>
TicketslackbotMon, 05 Dec 2016 18:06:27 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:15
http://meta.trac.wordpress.org/ticket/1515#comment:15
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by poena. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1480961184000155"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketrabmalinTue, 06 Dec 2016 07:47:35 GMTattachment sethttp://meta.trac.wordpress.org/ticket/1515
http://meta.trac.wordpress.org/ticket/1515
<ul>
<li><strong>attachment</strong>
set to <em>1515.diff</em>
</li>
</ul>
TicketrabmalinTue, 06 Dec 2016 07:48:24 GMTkeywords sethttp://meta.trac.wordpress.org/ticket/1515#comment:16
http://meta.trac.wordpress.org/ticket/1515#comment:16
<ul>
<li><strong>keywords</strong>
<em>has-patch</em> added
</li>
</ul>
<p>
Patch added.
</p>
TicketslackbotTue, 06 Dec 2016 07:49:49 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:17
http://meta.trac.wordpress.org/ticket/1515#comment:17
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1481010584000180"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketgrapplerulrichSat, 10 Dec 2016 16:58:24 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:18
http://meta.trac.wordpress.org/ticket/1515#comment:18
<p>
Thank you @rabmalin for working on this again. As it is plain text I feel it should be shorter so that people read it. I made a few changes. See the screenshot below how it would look like in the email.
</p>
<p>
<a style="padding:0; border:none" href="https://dl.dropboxusercontent.com/s/xutajko5rq89589/reveiw-email.jpeg"><img src="https://dl.dropboxusercontent.com/s/xutajko5rq89589/reveiw-email.jpeg" alt="https://dl.dropboxusercontent.com/s/xutajko5rq89589/reveiw-email.jpeg" crossorigin="anonymous" title="https://dl.dropboxusercontent.com/s/xutajko5rq89589/reveiw-email.jpeg" /></a>
</p>
TicketpoenaSat, 10 Dec 2016 17:04:58 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:19
http://meta.trac.wordpress.org/ticket/1515#comment:19
<p>
There needs to be some information on how to update the theme, since it is not obvious to first time authors. It is one of the most common questions.
</p>
TicketgrapplerulrichSat, 10 Dec 2016 20:21:05 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:20
http://meta.trac.wordpress.org/ticket/1515#comment:20
<p>
Good idea. Here is the latest text.
</p>
<pre class="wiki">Thank you for uploading %1$s to the WordPress Theme Directory. A ticket has been created for the review:
%2$s
** Requirements **
The theme must pass all the requirements to be included in the Theme Directory. The ticket will be closed if five or more errors are found.
&lt;https://make.wordpress.org/themes/handbook/review/required/&gt;
** Review Process **
To understand the review process better read the summary in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/&gt;
** Update **
You can update your theme any time and it will get added to the ticket. You can do so by uploading the new zip file.
https://wordpress.org/themes/getting-started/
** Help! **
You can help speed up the process by making sure that your theme follows all of the requirements, but also by becoming a reviewer.
&lt;https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/&gt;
** Questions? **
If you have questions you can ask the reviewer in the ticket or chat with us on Slack in the #themereview channel. &lt;https://chat.wordpress.org/&gt;
Subscribe to the blog to stay up to date with the latest requirements and the ongoing work to improve the review process:
&lt;https://make.wordpress.org/themes/&gt;
Thank you.
The WordPress Theme Review Team
</pre>
TicketslackbotTue, 13 Dec 2016 18:03:33 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:21
http://meta.trac.wordpress.org/ticket/1515#comment:21
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by grapplerulrich. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1481652210000860"><span class="icon">​</span>View the logs</a>.</em>
</p>
TicketjoedolsonTue, 13 Dec 2016 18:04:31 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:22
http://meta.trac.wordpress.org/ticket/1515#comment:22
<p>
Is it possible to add a note about the accessibility-ready process *if* the theme carries the accessibility-ready tag?
</p>
TicketgrapplerulrichTue, 13 Dec 2016 18:09:43 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:23
http://meta.trac.wordpress.org/ticket/1515#comment:23
<p>
We could use <code>in_array( 'accessibility-ready', $this-&gt;theme-&gt;get( 'Tags' ) )</code> to check if the theme is using the a11y-ready tag before adding the extra text.
</p>
TicketjoedolsonTue, 13 Dec 2016 18:10:32 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:24
http://meta.trac.wordpress.org/ticket/1515#comment:24
<p>
Example text:
</p>
<pre class="wiki">** Accessibility Ready **
Thanks for submitting an accessibility ready theme! Themes with the accessibility ready tag will go through a secondary review process to meet accessibility guidelines. Please review the guidelines in our handbook: &lt;https://make.wordpress.org/themes/handbook/review/accessibility/&gt;
</pre>
TicketgrapplerulrichTue, 13 Dec 2016 22:04:54 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:25
http://meta.trac.wordpress.org/ticket/1515#comment:25
<p>
Latest text. The a11y ready text needs to be wrapped in a conditional. <code>in_array( 'accessibility-ready', $this-&gt;theme-&gt;get( 'Tags' ) )</code>
</p>
<pre class="wiki">Thank you for uploading %1$s to the WordPress Theme Directory. A ticket has been created for the review:
%2$s
** Requirements **
The theme must pass all the requirements to be included in the Theme Directory. The ticket will be closed if five or more errors are found.
&lt;https://make.wordpress.org/themes/handbook/review/required/&gt;
** Accessibility Ready **
Thanks for submitting an accessibility ready theme! Themes with the accessibility ready tag will go through a secondary review process to meet accessibility guidelines. Please review the guidelines in our handbook: &lt;https://make.wordpress.org/themes/handbook/review/accessibility/&gt;
** Review Process **
To understand the review process, read the summary in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/&gt;
** Update **
You can update your theme any time and it will get added to the ticket. You can do so by bumping up your theme's version number and uploading a new ZIP file.
https://wordpress.org/themes/getting-started/
** Help! **
You can help speed up the process by making sure that your theme follows all of the requirements. You can also help by becoming a reviewer.
&lt;https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/&gt;
** Questions? **
If you have questions you can ask the reviewer in the ticket or chat with us on Slack in the #themereview channel. &lt;https://chat.wordpress.org/&gt;
Subscribe to the blog to stay up to date with the latest requirements and the ongoing work to improve the review process:
&lt;https://make.wordpress.org/themes/&gt;
Thank you.
The WordPress Theme Review Team
</pre>
Ticketdd32Wed, 14 Dec 2016 02:53:07 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:26
http://meta.trac.wordpress.org/ticket/1515#comment:26
<p>
For translation purposes, could we keep to a single email without branching?
</p>
<p>
For example, without branching and slotting the accessibility in under the review section
</p>
<pre class="wiki">Thank you for uploading %1$s to the WordPress Theme Directory. A ticket has been created for the review:
&lt;%2$s&gt;
** Requirements **
The theme must pass all the requirements to be included in the Theme Directory. The ticket will be closed if five or more errors are found.
&lt;https://make.wordpress.org/themes/handbook/review/required/&gt;
** Review Process **
To understand the review process, read the summary in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/&gt;
** Accessibility Ready **
If you've submitted a theme with the accessibility ready tag, it will go through a secondary review process to meet accessibility guidelines.
Please review the guidelines in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/accessibility/&gt;
** Theme Updates **
You can update your theme any time and it will be added to the ticket. You can do so by bumping up your theme's version number and uploading a new ZIP file.
&lt;https://wordpress.org/themes/getting-started/&gt;
** Help! **
You can help speed up the process by making sure that your theme follows all of the requirements. You can also help by becoming a reviewer.
&lt;https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/&gt;
** Questions? **
If you have questions you can ask the reviewer in the ticket or chat with us on Slack in the #themereview channel. &lt;https://chat.wordpress.org/&gt;
Subscribe to the Theme Review blog to stay up to date with the latest requirements and the ongoing work to improve the review process:
&lt;https://make.wordpress.org/themes/&gt;
Thank you.
The WordPress Theme Review Team
</pre><p>
For reference, a diff from <a class="ticket" href="http://meta.trac.wordpress.org/ticket/1515#comment:25" title="Comment 25">comment #25</a>: <a class="ext-link" href="https://www.diffchecker.com/ueRDrdZn"><span class="icon">​</span>https://www.diffchecker.com/ueRDrdZn</a>
</p>
TicketjuhiseWed, 14 Dec 2016 06:26:31 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:27
http://meta.trac.wordpress.org/ticket/1515#comment:27
<p>
I just made minor updates in text.
</p>
<pre class="wiki">Thank you for uploading %1$s to the WordPress Theme Directory. A ticket has been created for the review:
&lt;%2$s&gt;
** Requirements **
The theme must pass all the requirements to be included in the Theme Directory. The ticket will be closed if five or more different errors are found.
&lt;https://make.wordpress.org/themes/handbook/review/required/&gt;
** Review Process **
To understand the review process, read the summary in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/&gt;
** Accessibility Ready **
If you've submitted a theme with the accessibility ready tag, it will go through a secondary review process to meet accessibility guidelines.
Please review the guidelines in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/accessibility/&gt;
** Theme Updates **
You can update your theme any time and it will be added to the ticket. You can do so by bumping up your theme's version number in your style.css and uploading a new ZIP file.
&lt;https://wordpress.org/themes/getting-started/&gt;
** Help! **
You can help speed up the process by making sure that your theme follows all of the requirements. You can also help by becoming a reviewer.
&lt;https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/&gt;
** Questions? **
If you have questions you can ask the reviewer in the ticket or chat with us on Slack in the #themereview channel. &lt;https://chat.wordpress.org/&gt;
Subscribe to the Theme Review blog to stay up to date with the latest requirements and the ongoing work to improve the review process:
&lt;https://make.wordpress.org/themes/&gt;
Thank you.
The WordPress Theme Review Team
</pre><p>
Here diff can be seen <a class="ext-link" href="https://www.diffchecker.com/8GwTipzg"><span class="icon">​</span>https://www.diffchecker.com/8GwTipzg</a>
</p>
TicketpoenaWed, 14 Dec 2016 06:31:59 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:28
http://meta.trac.wordpress.org/ticket/1515#comment:28
<p>
Perhaps the Help! is not appropriate, it is a headline people would look for when they need help, not when they want to learn how to contribute.
</p>
TicketgrapplerulrichWed, 14 Dec 2016 08:09:17 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:29
http://meta.trac.wordpress.org/ticket/1515#comment:29
<p>
Ok, I think we are nearly there. I change the title from <code>help</code> to <code>contribute</code>. I think we can include the a11y text in all emails and improve on it again in the future.
</p>
<pre class="wiki">Thank you for uploading %1$s to the WordPress Theme Directory. A ticket has been created for the review:
&lt;%2$s&gt;
** Requirements **
The theme must pass all the requirements to be included in the Theme Directory. The ticket will be closed if five or more different errors are found.
&lt;https://make.wordpress.org/themes/handbook/review/required/&gt;
** Review Process **
To understand the review process, read the summary in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/&gt;
** Accessibility Ready **
If you've submitted a theme with the accessibility ready tag, it will go through a secondary review process to meet accessibility guidelines.
Please review the guidelines in our handbook:
&lt;https://make.wordpress.org/themes/handbook/review/accessibility/&gt;
** Theme Updates **
You can update your theme any time and it will be added to the ticket. You can do so by bumping up your theme's version number in your style.css and uploading a new ZIP file.
&lt;https://wordpress.org/themes/getting-started/&gt;
** Contribute! **
You can help speed up the process by making sure that your theme follows all of the requirements. You can also help by becoming a reviewer.
&lt;https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/&gt;
** Questions? **
If you have questions you can ask the reviewer in the ticket or chat with us on Slack in the #themereview channel. &lt;https://chat.wordpress.org/&gt;
Subscribe to the Theme Review blog to stay up to date with the latest requirements and the ongoing work to improve the review process:
&lt;https://make.wordpress.org/themes/&gt;
Thank you.
The WordPress Theme Review Team
</pre>
Ticketdd32Wed, 21 Dec 2016 00:47:21 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:30
http://meta.trac.wordpress.org/ticket/1515#comment:30
<p>
In <a class="changeset" href="http://meta.trac.wordpress.org/changeset/4561" title="Theme Directory: Update the post-submit-theme email with more details ...">4561</a>:
</p>
<div class="message"><p>
Theme Directory: Update the post-submit-theme email with more details of what Theme Authors should expect.<br />
</p>
<p>
Props grapplerulrich, rabmalin, kkoppenhaver, poena, joedolson, juhise, dd32. <br />
See <a class="new ticket" href="http://meta.trac.wordpress.org/ticket/1515" title="#1515: enhancement: Adding more info in the email sent after theme is submitted (new)">#1515</a>.<br />
</p>
</div>
Ticketdd32Wed, 21 Dec 2016 00:53:53 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:31
http://meta.trac.wordpress.org/ticket/1515#comment:31
<p>
I've gone ahead and updated the version currently sent out, as this looks pretty good to me, and it's been a week without other alterations.
</p>
<p>
I'm leaving this ticket open in the short term as it appears there may still be some small tweaks that others may want to be made.
For reference, here's what it looks like in gmail: <a class="ext-link" href="https://cloudup.com/cRsTDTkCfnE"><span class="icon">​</span>https://cloudup.com/cRsTDTkCfnE</a>
</p>
TicketsamuelsidlerWed, 21 Dec 2016 17:33:36 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:32
http://meta.trac.wordpress.org/ticket/1515#comment:32
<p>
Replying to <a class="ticket" href="http://meta.trac.wordpress.org/ticket/1515#comment:31" title="Comment 31">dd32</a>:
</p>
<blockquote class="citation">
<p>
I'm leaving this ticket open in the short term as it appears there may still be some small tweaks that others may want to be made.
For reference, here's what it looks like in gmail: <a class="ext-link" href="https://cloudup.com/cRsTDTkCfnE"><span class="icon">​</span>https://cloudup.com/cRsTDTkCfnE</a>
</p>
</blockquote>
<p>
Yeah... That doesn't look amazing. I'm assuming it's too much of a pain to send an HTML email, but maybe we can play around with formatting a bit more. I think <code>==</code> might be better than <code>**</code>, for example. And putting the URLs at the end of each paragraph (but still part of them) could be beneficial, depending on screen size.
</p>
TicketgrapplerulrichWed, 21 Dec 2016 17:46:44 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:33
http://meta.trac.wordpress.org/ticket/1515#comment:33
<blockquote class="citation">
<p>
I think <code>==</code> might be better than <code>**</code>
</p>
</blockquote>
<p>
I don't mind either way. We can try the <code>==</code> or even <code>##</code>
</p>
<blockquote class="citation">
<p>
And putting the URLs at the end of each paragraph (but still part of them) could be beneficial, depending on screen size.
</p>
</blockquote>
<p>
I prefer it this way more.
</p>
<p>
One thing I did see was having the a11y text all in one paragraph.
</p>
<p>
In the snippets above there were two lines of space between the paragraph. I feel that help would add a bit more white space.
</p>
Ticketdd32Thu, 22 Dec 2016 03:04:01 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:34
http://meta.trac.wordpress.org/ticket/1515#comment:34
<blockquote class="citation">
<p>
I'm assuming it's too much of a pain to send an HTML email
</p>
</blockquote>
<p>
We could do a once-off for this if someone wants to write up a patch for it, but a text-only fallback would still be needed.
</p>
<p>
The double paragraph spacing was causing a bit of weirdness for me, but I can't recall what the actual problem was. Forcing that is easy enough though.
What's the consensus for the rest? Links inline, use some other format for headings?
</p>
TicketslackbotWed, 25 Jan 2017 07:12:06 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:35
http://meta.trac.wordpress.org/ticket/1515#comment:35
<p>
<em>This ticket was mentioned in <a class="ext-link" href="https://make.wordpress.org/chat/"><span class="icon">​</span>Slack</a> in #themereview by rabmalin. <a class="ext-link" href="https://wordpress.slack.com/archives/themereview/p1485328323006183"><span class="icon">​</span>View the logs</a>.</em>
</p>
Ticketdingo_bastardWed, 25 Jan 2017 08:05:57 GMThttp://meta.trac.wordpress.org/ticket/1515#comment:36
http://meta.trac.wordpress.org/ticket/1515#comment:36
<p>
Did anybody tried to add <code>*</code> around the headings (instead of <code>** Requirements **</code> just <code>*Requirements*</code>)? I've read that some email clients can interpret that as bold (and <code>_</code> as underline). Also I'd remove <code>&lt;&gt;</code> around the links, looks odd to me. Plain links are fine.
</p>
<p>
Just my 2 cents :)
</p>
TickettellyworthThu, 14 Feb 2019 02:39:00 GMTmilestone sethttp://meta.trac.wordpress.org/ticket/1515#comment:37
http://meta.trac.wordpress.org/ticket/1515#comment:37
<ul>
<li><strong>milestone</strong>
set to <em>Q1</em>
</li>
</ul>
Ticket