<div dir="ltr"><a href="http://make.wordpress.org/themes/2012/11/26/wordpress-3-5-guidelines-revisions/" target="_blank" style="font-family:arial,sans-serif;font-size:13px">http://make.wordpress.org/themes/2012/11/26/wordpress-3-5-guidelines-revisions/</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 12, 2013 at 10:56 AM, Philip M. Hofer (Frumph) <span dir="ltr"><<a href="mailto:philip@frumph.net" target="_blank">philip@frumph.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div style="font-size:12pt;font-family:'Calibri'">
<div>@Thomas where are you getting the information that shortcodes are not
allowed?</div>
<div> </div>
<div> </div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">
<div style="FONT:10pt tahoma">
<div> </div>
<div style="BACKGROUND:#f5f5f5">
<div><b>From:</b> <a title="contact@themezee.com" href="mailto:contact@themezee.com" target="_blank">Thomas from ThemeZee</a> </div>
<div><b>Sent:</b> Wednesday, June 12, 2013 7:39 AM</div>
<div><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
</div><div class="im">
<div><b>Subject:</b> Re: [theme-reviewers] Questions on my first
review</div></div></div></div>
<div> </div></div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>Sorry Chip, I don't saw your last email until now. Stupid Gmail
Import..<br><br></div>I know the Presentation vs Functionality Guideline, but
this guideline is really unclear worded for me. I only understand it know
because I have followed the mailing list here for some time. Since then I know
most things I can include in my themes and what not. I'm no native speaker so
maybe it's just that ;)<br><br></div>I agree that the guideline can not list
every possible issue, but a few examples below the guidelines would be nice.
<br><br></div>
<div></div>
<div>Post Content Shortcodes are not allowed. <br></div>Custom Post Types not
allowed (except for special use cases?)<br></div>Functionality which is not
presentational like Tracking Codes, SEO Options ...<br><br></div>As you have
said every human interprets the guidelines differently. Therefore they should be
as clear as possible to make the theme reviews as consistent as possible.
<br><br></div>That is just my opinion, I don't want to offend anyone
;)<br></div></div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/6/12 Thomas from ThemeZee <span dir="ltr"><<a href="mailto:contact@themezee.com" target="_blank">contact@themezee.com</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">
<div>
<div>Ah of course shortcodes and CPTs should always be forbidden because they
cause really high lock-in effects, but there are also lock-in effects
(although they're smaller) of Google Analytics and SEO options.
<br><br></div>My email should not induce that these things should be allowed,
I just want a clear guideline :)<br><br></div>Best
Regards,<br>Thomas<br></div>
<div>
<div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/6/12 Thomas from ThemeZee <span dir="ltr"><<a href="mailto:contact@themezee.com" target="_blank">contact@themezee.com</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">
<div>
<div>
<div>
<div>
<div>Allowing {plugin-territory-stuff} now (even if it's disabled by
default) would have the effect that theme developers are allowed to also
include shortcodes and custom post types in their themes.
<br><br></div>After all in my opinion shortcodes and CPTs are more
presentational than sharing buttons, google analytics and SEO. I had planned
to include a simple image slideshow based on CPTs a few month ago and was
turned down.<br><br></div>And it was a good thing. It took me some time but
now I truly believe that themes should not include any plugin territory
features. Therefore I would suggest to continue the {plugin-territory-stuff}
is strictly forbidden policy..<br><br></div>The only thing that really bugs
me is that there is no guideline and no consistent rules. The result is that
their are hundred of themes which have a lot of plugin stuff in their themes
and other themes are rejected for the exact same features. <br><br></div>
<div>I can live with both {plugin-territory-stuff} is allowed or not, but it
should be stated clearly in the guidelines and applied by all theme
reviewers.<br></div>
<div> </div>Just my 2 cents<span><font color="#888888"><br></font></span></div><span><font color="#888888">Thomas<br></font></span></div>
<div>
<div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/6/12 Peter Kakoma <span dir="ltr"><<a href="mailto:kakomap@gmail.com" target="_blank">kakomap@gmail.com</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">
<div>The issue is that there is no definitive guideline about
{plugin-territory-stuff}. I believe the end-goal of this discussion is to
draft one and share it with the rest of the world (otherwise we'll be
discussing this again two months from now when a first-time reviewer asks
the same question)<br><br></div>And in as much as my theme is guilty of
adding Analytics, I agree with you-the line should be drawn at
non-presentational stuff (*cough* SEO, *cough*). Removing Analytics now,
updating the theme.<br></div>
<div class="gmail_extra">
<div>
<div><br><br>
<div class="gmail_quote">On Wed, Jun 12, 2013 at 4:06 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">I don't agree that the Favicon guidelines are appropriate
for extending to all {plugin territory} functionality.
<div>
<div> </div>
<div>Things that are marginally presentational (e.g. sharing links)?
Using the Favicon guidelines as a model is reasonable. But Google
Analytics: no reason to facilitate Themes adding this functionality.
It's not in any way whatsoever presentational. As far as I'm concerned,
that's an absolute line of demarcation. If it's not in any way
presentational, it doesn't belong in a Theme, opt-in/disabled-by-default
or otherwise.</div></div></div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">
<div>
<div>On Wed, Jun 12, 2013 at 8:37 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span>
wrote:<br></div></div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>
<div>
<div dir="ltr">
<div>
<div class="gmail_extra">
<div> </div>
<div class="gmail_quote">On Wed, Jun 12, 2013 at 2:46 AM, Peter Kakoma
<span dir="ltr"><<a href="mailto:kakomap@gmail.com" target="_blank">kakomap@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">
<li>Themes are recommended not to implement custom
{plugin-territory-stuff} functionality. <br>
</li><li>If implemented, {plugin-territory-stuff} functionality is
required to be opt-in, and disabled by default. <br>
</li><li>If implemented, {plugin-territory-stuff} functionality is
required to support user-defined {plugin-territory-stuff}
images</li></blockquote></div>
<div> </div></div></div>
<div class="gmail_extra">Those points are fairly well sorted except for
the third which is really more relevant to the original ideas behind
the use of favicons, but if you use the first two points as your
benchmark then you should be (for the most part but not 100%
guaranteed) fine with going forward.<span><font color="#888888"><br><br></font></span></div><span><font color="#888888">
<div class="gmail_extra">
<div> </div>
<div>Edward Caissie<br>aka Cais.</div></div></font></span></div>
<div> </div></div></div>
<div>_______________________________________________<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></div></blockquote></div>
<div> </div></div><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></blockquote></div><br><br clear="all"><br></div></div><span><font color="#888888">-- <br><a href="http://www.urbanlegendkampala.com" target="_blank">www.urbanlegendkampala.com</a><br></font></span></div><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></blockquote></div>
<div> </div></div></div></div></blockquote></div>
<div> </div></div></div></div></blockquote></div>
<div> </div></div>
</div></div><p>
</p><hr><div class="im">
_______________________________________________<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><p></p></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><br></div>