<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"><FONT
size=3 face=Calibri>They stumble over it because it’s the reviewers
determination to whether or not they warrant being in a plugin and not in the
theme.</FONT></DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"> </DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">It’s
not a black and white.</DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"> </DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">Jeeze,
imagine a single plugin for a theme that does an output of theme content in a
shortcode that’s specific for that theme, .. uh what use is that ?</DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"> </DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">seriously.</DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"> </DIV></DIV>
<DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none"></DIV>
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=contact@themezee.com
href="mailto:contact@themezee.com">Thomas from ThemeZee</A> </DIV>
<DIV><B>Sent:</B> Tuesday, April 30, 2013 2:07 AM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A>
</DIV>
<DIV><B>Subject:</B> Re: [theme-reviewers] Coding Standard</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>
<DIV>
<DIV>
<DIV>
<DIV>Hi everybody,<BR><BR></DIV>in my opinion the Guidelines should clearly
point out that Shortcodes and Custom Post Types are not allowed to use in
themes. This is a point where both reviewers and theme authors often stumble
over.<BR><BR></DIV>I know we have the passage: "Since the purpose of Themes is
to define the presentation of user content, Themes must not be used to define
the generation of user content, or to define Theme-independent site options or
functionality." <BR><BR>But most people misinterpret this passage or
overread it or maybe don't realize what it means - I don't know - but we had the
discussion about Shortcodes and CPTs a lot lateley. I had to ask about it a few
weeks ago and I have contributed some themes to the directory a long time
before. <BR><BR>The Guidelines already contain a clear phrase that TimThumb is
not allowed, I would suggest that there is a similiar phrase in the Guidelines
which forbid shortcodes and CPTs.<BR><BR></DIV>Best
Regards,<BR></DIV>Thomas<BR></DIV>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>2013/4/29 Chip Bennett <SPAN dir=ltr><<A
href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>></SPAN><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>
<DIV dir=ltr>This.
<DIV> </DIV>
<DIV>The Guidelines - i.e. the things that are *required* - are in one place
only: the Theme Review Codex page:</DIV>
<DIV><A href="http://codex.wordpress.org/Theme_Review"
target=_blank>http://codex.wordpress.org/Theme_Review</A><BR></DIV>
<DIV> </DIV>
<DIV>The Make/Themes site is used to discuss the guidelines; if anything is
formalized, it will be added to the Codex page. There are things that we
occasionally miss, so if you have any specific Guidelines that were decided on
the Make/Themes site, but not added to the Codex, please bring them up, and
we'll make sure the Codex is accurate.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Chip</DIV></DIV>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_extra><BR><BR>
<DIV class=gmail_quote>On Mon, Apr 29, 2013 at 5:35 PM, Amy Hendrix <SPAN
dir=ltr><<A href="mailto:sabreuse@gmail.com"
target=_blank>sabreuse@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>If that's a common occurrence (and I haven't been
reviewing enough<BR>lately to know how common it really is), then that's a
MAJOR problem.<BR>The Make site is where changes to the guidelines are
*discussed*, but<BR>it's the nature of such discussions that not all points
that are<BR>discussed are actually adopted as guidelines.<BR><BR>To put it
bluntly, reviewers, please DO NOT say things are required if<BR>they aren't
actually required in the Review Guidelines. Passing the<BR>review process is
difficult already; we absolutely need to have a<BR>clear and consistently
enforced set of guidelines. There are enough<BR>complaints out there that
the guidelines are arbitrary and constantly<BR>changing without people
saying things are required when they're not.<BR>
<DIV>
<DIV><BR>On Mon, Apr 29, 2013 at 5:29 PM, Srikanth Koneru <<A
href="mailto:tskk79@gmail.com" target=_blank>tskk79@gmail.com</A>>
wrote:<BR>> can't recall any instantly, but reviewers usually point to
make site and<BR>> state that its a required issue even tough its not
mentioned on org<BR>> guidelines.<BR>><BR>><BR>> On Tue, Apr 30,
2013 at 2:56 AM, Chip Bennett <<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>> wrote:<BR>>><BR>>>
What policies, specifically?<BR>>><BR>>><BR>>> On Mon, Apr
29, 2013 at 5:25 PM, Srikanth Koneru <<A href="mailto:tskk79@gmail.com"
target=_blank>tskk79@gmail.com</A>>
wrote:<BR>>>><BR>>>> A few policies are formulated on make
site but they don't make it to<BR>>>> guidelines on
.org<BR>>>> so these policies are only recommended
then?<BR>>>><BR>>>><BR>>>> On Tue, Apr 30, 2013
at 2:53 AM, Chip Bennett <<A href="mailto:chip@chipbennett.net"
target=_blank>chip@chipbennett.net</A>><BR>>>>
wrote:<BR>>>>><BR>>>>> Yes. At the moment, the
Coding and CSS standards are only *recommended*.<BR>>>>> Making
them *required* may be a bridge we cross at some point, but we're
not<BR>>>>> there right
now.<BR>>>>><BR>>>>><BR>>>>> On Mon, Apr
29, 2013 at 5:07 PM, Emil Uzelac <<A href="mailto:emil@uzelac.me"
target=_blank>emil@uzelac.me</A>>
wrote:<BR>>>>>><BR>>>>>> If this does not
cause any issues, I would say
recommended.<BR>>>>>><BR>>>>>>
Emil<BR>>>>>><BR>>>>>><BR>>>>>>
On Mon, Apr 29, 2013 at 3:53 PM, Stephen Cui <<A
href="mailto:scui2005@gmail.com"
target=_blank>scui2005@gmail.com</A>><BR>>>>>>
wrote:<BR>>>>>>><BR>>>>>>>
Hi,<BR>>>>>>><BR>>>>>>> During the theme
review, my theme has a "required issue" for next<BR>>>>>>>
version:<BR>>>>>>><BR>>>>>>> There are
inconsistency in spacing around parenthesis throughout
the<BR>>>>>>> theme. Recommend to read the WordPress? PHP
coding
standards.<BR>>>>>>><BR>>>>>>><BR>>>>>>>
<A
href="http://make.wordpress.org/core/handbook/coding-standards/php/#space-usage"
target=_blank>http://make.wordpress.org/core/handbook/coding-standards/php/#space-usage</A><BR>>>>>>><BR>>>>>>>
I have no problem to make such changes as it is good practice. I
also<BR>>>>>>> take the chance to revisit the
code.<BR>>>>>>><BR>>>>>>> My question is
" is it required?" or "just
recommended".<BR>>>>>>><BR>>>>>>>
Regards<BR>>>>>>><BR>>>>>>>
Stephen<BR>>>>>>><BR>>>>>>>
_______________________________________________<BR>>>>>>>
theme-reviewers mailing list<BR>>>>>>> <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>>>>>>>
<A href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>>>>>>><BR>>>>>><BR>>>>>><BR>>>>>>
_______________________________________________<BR>>>>>>
theme-reviewers mailing list<BR>>>>>> <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>>>>>>
<A href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>>>>>><BR>>>>><BR>>>>><BR>>>>>
_______________________________________________<BR>>>>>
theme-reviewers mailing list<BR>>>>> <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>>>>> <A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>>>>><BR>>>><BR>>>><BR>>>>
_______________________________________________<BR>>>>
theme-reviewers mailing list<BR>>>> <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>>>> <A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>>>><BR>>><BR>>><BR>>>
_______________________________________________<BR>>> theme-reviewers
mailing list<BR>>> <A
href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>>> <A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>>><BR>><BR>><BR>>
_______________________________________________<BR>> theme-reviewers
mailing list<BR>> <A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR>> <A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR>><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A href="mailto:theme-reviewers@lists.wordpress.org"
target=_blank>theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV><BR>_______________________________________________<BR>theme-reviewers
mailing list<BR><A
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</A><BR><A
href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers"
target=_blank>http://lists.wordpress.org/mailman/listinfo/theme-reviewers</A><BR><BR></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV>
<P>
<HR>
_______________________________________________<BR>theme-reviewers mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></DIV></DIV></DIV></BODY></HTML>