Every time I browse new, featured, or recently updated themes in the dashboard, I cringe because there are always instances of WordPress, wordpress, and Word press in the descriptions of the themes provided by the authors. In the absence of capital_p_dangit, could you guys add it to the checklist to do a quick proofreading of the description in style.css to make sure they spell WordPress correctly? It will help prevent my crow’s feet from getting worse. 
Thanks!
Tagged: description Toggle Comment Threads | Keyboard Shortcuts
-
Jen Mylo
Nitin Reddy 5:27 am on February 16, 2012 Permalink |
Perhaps I should write a plugin that auto-corrects the casing of “WordPress” in the descriptions, assuming there’s a hook for it, if course
Emil Uzelac 5:46 am on February 16, 2012 Permalink |
@Nitin Autocorrect will not work in style.css, nothing will unfortunately. This is something we need to do manually and it can be a requirement. http://codex.wordpress.org/Function_Reference/capital_P_dangit.
As one of the admins/reviewers I think that this is very important, therefore it’s added in Theme Review as well: http://codex.wordpress.org/Theme_Review#Capitol_.22P.22_in_WordPress_.28capital_p_dangit.29
If anyone else have better wording, feel free to change it. But that should be all right for now.
Cheers,
Emil
Edward Caissie 1:42 pm on February 16, 2012 Permalink |
There may be more significant consistency issues to address in the Theme Review process, but having WordPress spelled correctly is a rather straight forward request to be followed through with.
Although I must admit I may not necessarily “not-approve” a theme for inclusion into the Extend repository if the only issue was misspelling WordPress in the theme description but it would be a required correction to be made in future releases of the theme.
PS: @emiluzelac I did adjust the text and title of the new guideline you added … http://codex.wordpress.org/Theme_Review#Capital_.22P.22_in_WordPress_.28capital_p_dangit.29
Emil Uzelac 7:43 pm on February 16, 2012 Permalink |
not a problem @cais that looks far more professional!
Chip Bennett 2:41 pm on February 16, 2012 Permalink |
IMHO this is completely a bikeshed issue, and I think that the reviewers have far more important matters to worry about. If it must be a consideration, then put it in Theme Check, and make it a blocker in the upload script, so that the reviewers don’t have to bother with it.
Jane Wells 6:27 pm on February 16, 2012 Permalink |
Yes and no. It’s not a functional issue in terms of theme quality, but is in an issue in terms of trademark and quality control for wordpress.org. A code-based solution would be ideal and I can ask @otto42 if he can come up with something, but in the meantime, taking 2 seconds to look at that paragraph in the style.css file and shooting an email a la “Hey, you may not have realized, but you misspelled WordPress in your theme description. Could you please update it so that it is always spelled ‘WordPress’ in your description? Thanks!”
It’s not really something to occasion worry, but it is a quality control issue.
Emil Uzelac 7:31 pm on February 16, 2012 Permalink |
If we do this let’s say, e-mailing the author’s and ask them to modify capital_p_dangit, will you be giving us @wordpress.org e-mail addresses, at least for admins? The reason why is simple, people don’t even respond when we e-mail them from our own addresses. I don’t blame them, I wouldn’t even bother responding to an e-mail address that doesn’t comes from WordPress itself because it’s looks and sounds like either SPAM or some type of phishing.
Edward Caissie 7:34 pm on February 16, 2012 Permalink |
If @otto42 is going to be tasked with finding a “code-based solution” to this issue, I would also suggest someone is tasked with finding a “code-based solution” to scraping the repository theme descriptions etc. and sending out a bulk email requesting theme authors make these “required” corrections.
Emil Uzelac 7:42 pm on February 16, 2012 Permalink |
+1
Chip Bennett 7:49 pm on February 16, 2012 Permalink |
Wait: why would we need to send emails when we can just post a comment in the review ticket?
If you’re referring to a retrospective review of descriptions of currently approved Themes: not going to happen. Especially considering that we still cannot clear the current review queue, such effort would be alarmingly counter-productive.
Edward Caissie 10:31 pm on February 16, 2012 Permalink |
My understanding is this is for *all* themes in the repository … including those prior to the WPTRT inception.