<p>All I can say is that this is a Theme review team, not plugins. Themes in my personal opinion are just that, Themes, not plugins. In this discussion, please, let's review Themes and not throw everything into plugin territory. As always, this is my own opinion. Disagree? Fine and pretty soon you will be able and ok to submit CSS only. Note that I am not taking any side, only what I personally think is right. Of course you are more than welcome to pass or support my own opinion. :) BTW how many of you make a living out of Themes? Once again, plugins are different discussion list and I don't need to remind that this is WTRT.</p>
<div class="gmail_quote">On Jul 15, 2013 12:52 AM, "Philip M. Hofer (Frumph)" <<a href="mailto:philip@frumph.net">philip@frumph.net</a>> wrote:<br type="attribution"><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>There are two sides of the fence on this subject, those who feel that
themes should not include anything that a plugin can do; which is
fine. There’s really nothing wrong with that method of
thinking. The OTHER side, which includes myself and Emil and a bunch of
others do not really think that it’s a necessity to police those particular
things. A theme doesn’t have to be cross compatible in every way
except the way that the theme unit looks. Any extra feature to a theme is
just that, a bonus. Whether someone switches theme’s constantly
makes no difference. </div>
<div> </div>
<div>A HUGE majority of themes that are being used are actually commercial
themes: <a title="http://wordpress.org/themes/commercial/" href="http://wordpress.org/themes/commercial/" target="_blank">http://wordpress.org/themes/commercial/</a></div>
<div> </div>
<div>Those when switching to one theme or another will have some things no
longer work – and that is fine. There are plenty of ways, avenues and
programming that you can take to include those features into the theme you
switch to.</div>
<div> </div>
<div>The BIGGEST idea about that the don’t-worry-about-it group’s main objective
is to make the theme review process easier and faster to get
through. The biggest thing that people get hung up on returning day
after day to review themes is how time consuming they are to go
through. We also believe that it’s not the theme review team’s
responsibility to control that aspect of allowing a theme to have a feature or
not, that is up to the core dev’s to make that determination.</div>
<div> </div>
<div>Use all of the plugins, theme unit test and requirements for the backlinks
and other things. Do the cursory views of everything that’s
important and move em through the review process. </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="emil@uzelac.me" href="mailto:emil@uzelac.me" target="_blank">Emil Uzelac</a> </div>
<div><b>Sent:</b> Sunday, July 14, 2013 5:59 PM</div>
<div><b>To:</b> <a title="theme-reviewers@lists.wordpress.org" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">Discussion list for WordPress
theme reviewers.</a> </div>
<div><b>Subject:</b> Re: [theme-reviewers] Webmaster Tools IDs - plugin
territory?</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 dir="ltr">No worries, it's all good. So here it is, one example:
<div><a href="http://codex.wordpress.org/Settings_API" target="_blank">http://codex.wordpress.org/Settings_API</a>
excluding "Cowboy Coding" </div>
<div>there should not be any issues with that.</div>
<div> </div>
<div>Or even better:</div>
<div><a href="https://codex.wordpress.org/Theme_Customization_API" target="_blank">https://codex.wordpress.org/Theme_Customization_API</a><br></div>
<div> </div></div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <span dir="ltr"><<a href="mailto:prodevstudio@gmail.com" target="_blank">prodevstudio@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 there is no core api for this kind of
option/configuration then how does a developer add those properly? (I am not
picking on you Emil so don't take it personally)
<div> </div>
<div>IMO these options are equivalent to robot.txt which is taken care of in
core.</div>
<div> </div>
<div>In my view these are site configuration and theme should stay out of
them. It has nothing to do with presentation.</div>
<div> </div>
<div><span style="LINE-HEIGHT:normal">WPTRT</span><span> could</span><span>
propose that if a </span><span>theme is going to provide an</span><span>
interface to set these value </span><span>they need to be stores such a way
that it can transfer from theme to theme and even plugins. WPTRT needs provide
those guidelines in where and how these config stored/retrived. so that
user/site is not <span></span>impacted adversely when switching
themes.</span><br></div>
<div> </div>I know not everyone will agree to above but it is in the best
interest of the end user.
<div> </div>
<div>Regards,</div>
<div> </div>
<div>Azizur
<div>
<div>
<div> </div>
<div><br><br>On Monday, 15 July 2013, Emil Uzelac wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">Hi Jason,
<div> </div>
<div>Assuming that we're referring to Theme Options, this should be
fine.</div>
<div> </div>
<div><i>As long as this is not hardcoded and properly added :)</i></div>
<div> </div>
<div>Thanks,</div>
<div>Emil </div></div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <span dir="ltr"><<a>jgc@jasonclarke.org</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Hi Admins,
<div> </div>
<div>Long-time listener, first-time caller here- in reviewing my first
theme, I remembered a recent list discussion on how Analytics-specific
fields in themes are not allowed because they're considered plugin
territory.</div>
<div> </div>
<div>On a related note, I'm assuming that other similar fields such as
"Google Webmaster Tools ID" and "Alexa ID" are also plugin territory- can
the admins confirm this is the case?</div>
<div> </div>
<div>Thank you!</div>
<div>Jason</div>
<div> </div>
<div>PS - As a side/related note, it would be super helpful if the list
archives where somehow searchable - that might be one more avenue for
newbies like myself to check before emailing the list (assuming guidelines
haven't changed).<span><font color="#888888"><br clear="all">
<div> </div>-- <br>Jason Clarke<br><a href="http://jasonclarke.org" target="_blank">http://jasonclarke.org</a><br><br>************************<br></font></span></div><br>_______________________________________________<br>
theme-reviewers
mailing list<br><a>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></blockquote></div></div></div></div><span><font color="#888888"><br><br>-- <br>Sent from Gmail
Mobile<br></font></span><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>
<p>
<hr>
_______________________________________________<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>
</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>