[theme-reviewers] Tags and description.

[Chip Bennett]

I definitely see benefit in a both/and approach, rather than either/or, to
"e-commerce" and "plugin-support-{plugin}" tags. And in all honesty,
getting a generic "e-commerce" tag approved is probably easier and more
feasible in the short-term.

But I'd still like to see some standard way for Themes to declare that
support, since if the "e-commerce" tag is added, a reviewer is going to
have to verify the tag is appropriate. A simple add_theme_support(
'plugin-name' ) call would meet that requirement very nicely.


On Fri, Aug 23, 2013 at 2:43 PM, Justin Tadlock <justin at justintadlock.com>wrote:

> I'm re-posting this because my last email went to moderation for file
> size.  I'm not sure who's in charge of that.
>
> I like the idea of automation for plugin support.  We just need plugins
> and themes to start talking to each other via add_theme_support(), which
> seems to be a growing standard.
>
> ***
>
> To answer the question of "what is an e-commerce theme?" I'd say any theme
> that's built to support any e-commerce plugin. We shard start creating a
> set of guidelines that define these tags.  Maybe we won't have all the
> answers, but we can at least start formulating a standard to go by.
>
> What's going to be even more useful is themes getting the same
> "readme.txt" treatment that plugins get.  It would help expand on, say,
> what e-commerce solution(s) it supports.
>
> Not all users look for a WooCommerce, JigoShop, or whatever theme to start
> out.  Many of them don't really know they'll need both a plugin and theme
> for an e-commerce site.  So, they go out looking for a theme.  They know
> they want to run an e-commerce site.  We should provide a way for them to
> find the solution they're looking for.  Having a generic e-commerce tag
> would go a long way in helping them.
>
> E-commerce is just one of several tags though.  We should focus on what
> tags we can feasibly define to some degree and come up with a list.
>
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130823/ecb2779a/attachment.html>