[theme-reviewers] Webmaster Tools IDs - plugin territory?

Mon Jul 15 07:31:31 UTC 2013

Curious question, Is the theme directory for users or theme authors? I mean
who's interest does it serve first?

On Mon, Jul 15, 2013 at 12:57 PM, Emil Uzelac <emil at uzelac.me> wrote:

> In this list author goes before user and if I have to say anything about
> that this cannot change. Yes, we should think of them as well, but if
> author does not break the core, the Theme or does not cowboy code, please
> let's make everyone's life easier and not push plugin territory for just
> about everything. I am not going against admin nor taking authors side,
> please make a big note of that.
>
> My stand will probably change if WPORG says that this what I am saying is
> wrong or no longer accepted. For time being, lets make beautiful Themes and
> ease the guidelines just a bit. WordPress is freedom, not prison. :)
> On Jul 15, 2013 2:09 AM, "Harish" <me at harishchouhan.com> wrote:
>
>> I have to agree on this with Emil. Currently the way themes are reviewed
>> is resulting the end quality of code being better in WordPress repo than
>> many themes on premium marketplaces. ****
>>
>> ** **
>>
>> But this constant thing about what to have in theme and what not to have
>> is too limiting. Shortcodes, etc. are no doubt out of the question and
>> plugin territory, but these small things such as ability to add Google
>> verification code, GA code, etc. are very helpful for someone new. ****
>>
>> ** **
>>
>> Those who have experience enough will install a plugin for the same
>> anyways.****
>>
>> ** **
>>
>> ** **
>>
>> ** **
>>
>> Regards,****
>>
>> Harish Chouhan****
>>
>> ** **
>>
>> *Visit me at *- www.harishchouhan.com
>>
>> **
>>
>> ** **
>>
>> *From:* theme-reviewers [mailto:
>> theme-reviewers-bounces at lists.wordpress.org] *On Behalf Of *Emil Uzelac
>> *Sent:* Mon 15 July 13 12:30 PM
>> *To:* Discussion list for WordPress theme reviewers.
>> *Subject:* Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?*
>> ***
>>
>> ** **
>>
>> 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.****
>>
>> On Jul 15, 2013 12:52 AM, "Philip M. Hofer (Frumph)" <philip at frumph.net>
>> wrote:****
>>
>> 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. ****
>>
>>  ****
>>
>> A HUGE majority of themes that are being used are actually commercial
>> themes: http://wordpress.org/themes/commercial/****
>>
>>  ****
>>
>> 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.****
>>
>>  ****
>>
>> 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.****
>>
>>  ****
>>
>> 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.  ****
>>
>>  ****
>>
>>  ****
>>
>>  ****
>>
>> *From:* Emil Uzelac <emil at uzelac.me> ****
>>
>> *Sent:* Sunday, July 14, 2013 5:59 PM****
>>
>> *To:* Discussion list for WordPress theme reviewers.<theme-reviewers at lists.wordpress.org>
>> ****
>>
>> *Subject:* Re: [theme-reviewers] Webmaster Tools IDs - plugin territory?*
>> ***
>>
>>  ****
>>
>> No worries, it's all good. So here it is, one example: ****
>>
>> http://codex.wordpress.org/Settings_API excluding "Cowboy Coding" ****
>>
>> there should not be any issues with that.****
>>
>>  ****
>>
>> Or even better:****
>>
>> https://codex.wordpress.org/Theme_Customization_API****
>>
>>  ****
>>
>> ** **
>>
>> On Sun, Jul 14, 2013 at 7:55 PM, Azizur Rahman <prodevstudio at gmail.com>
>> wrote:****
>>
>> 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) ****
>>
>>  ****
>>
>> IMO these options are equivalent to robot.txt which is taken care of in
>> core.****
>>
>>  ****
>>
>> In my view these are site configuration and theme should stay out of
>> them. It has nothing to do with presentation.****
>>
>>  ****
>>
>> WPTRT could propose that if a theme is going to provide an interface to
>> set these value 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
>> impacted adversely when switching themes.****
>>
>>  ****
>>
>> I know not everyone will agree to above but it is in the best interest of
>> the end user. ****
>>
>>  ****
>>
>> Regards,****
>>
>>  ****
>>
>> Azizur ****
>>
>>  ****
>>
>>
>>
>> On Monday, 15 July 2013, Emil Uzelac wrote:****
>>
>> Hi Jason, ****
>>
>>  ****
>>
>> Assuming that we're referring to Theme Options, this should be fine.****
>>
>>  ****
>>
>> *As long as this is not hardcoded and properly added :)*****
>>
>>  ****
>>
>> Thanks,****
>>
>> Emil ****
>>
>> ** **
>>
>> On Sun, Jul 14, 2013 at 6:28 PM, Jason Clarke <jgc at jasonclarke.org>
>> wrote:****
>>
>> Hi Admins, ****
>>
>>  ****
>>
>> 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.****
>>
>>  ****
>>
>> 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?****
>>
>>  ****
>>
>> Thank you!****
>>
>> Jason****
>>
>>  ****
>>
>> 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).
>> ****
>>
>>  ****
>>
>> --
>> Jason Clarke
>> http://jasonclarke.org
>>
>> ****************************
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers****
>>
>>  ****
>>
>>
>>
>> --
>> Sent from Gmail Mobile
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers****
>>
>>  ****
>> ------------------------------
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers****
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers****
>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130715/0da324ca/attachment-0001.html>