[theme-reviewers] Tags and description.

Fri Aug 23 04:34:37 UTC 2013

@justin agreed.

We ned to think about more than just mobile/responsive/etc tags.

What about tags based one end purpose, how do we feel about reviewing
those? For instance theme forest has these top level categories for their
WordPress themes: Blog/ magazine, creative, corporate, retail, technology,
nonprofit, entertainment, miscellaneous, mobile, buddypress, and ecommerce.
Could we do tags like that? What about a CMS tag?

@emil - There is no guarantee that there will be new tags. This process is
very preliminary. But if a useful set of tags can be generated by the THX38
project, then a new search filtering system based on those tags will have a
good shot at being implemented.
I'm trying to take some initiative to bring the theme review team's
thoughts on tags back to the THX38 team because I'm the only theme reviewer
that was present for the first THX38 meeting and a lot of ideas for new
tags were thrown around, which made me worry about how we were going to
review them. Basically, I'd rather say, "this is what the theme review team
discussion resulted in", then say, "as one of the theme reviewers this is
what I think."

On Fri, Aug 23, 2013 at 12:16 AM, Justin Tadlock
<justin at justintadlock.com>wrote:

>  I agree with Chip that one tag would be better for end users.  However, I
> also think we need to propose multiple tags to whoever is in charge of
> this.  So, having a list of potential tags with their definitions is what
> we should put together.
>
> On that note, I've never had a user ask for an "adaptive" theme.  It's
> mostly "responsive."  But, "mobile-ready" and "mobile-first" are terms that
> are also thrown around a bit.
>
> Also, I dislike the phrase "fluid grid system" when referring to
> responsive design.  Maybe something along the lines of "a fluid layout that
> responds to screen size."  Anyway, I'm just nit-picking words here.
>
>
> On 8/22/2013 10:52 PM, Josh Pollock wrote:
>
> @chip- I think there is a good chance of a lot of new tags being added.
> Everyone agrees we need to be able to filter search results based on tags
> and the current set of tags doesn't do it.
>
>  What does it hurt to create a list of tag and definitions that the theme
> review team thinks would be useful and we could review fairly?
>
>  I think it would be better if we brainstormed a list without any
> premptive doomsaying, so I can take it back to the THX38 meeting as the
> theme review teams ideas on new tags, instead of just bringing own ideas.
>
> On Thursday, August 22, 2013, Chip Bennett wrote:
>
>> My main problem with that is that it's still adding three tags where
>> currently none exist. I just don't see that flying with the powers-that-be.
>> I think our best bet of getting *any* tags added is to keep to a single
>> tag.
>>
>>  IMHO, the tag list could probably stand for a bit of an overhaul - but
>> that would be a bigger discussion than this one.
>>
>>
>> On Thu, Aug 22, 2013 at 8:27 PM, Josh Pollock <jpollock412 at gmail.com>wrote:
>>
>> How about this:
>>
>>  Responsive: "A theme with a layout that employs a fluid grid system
>> that changes in response to screen size."
>> Mobile-Optimized: "A theme that adjusts its layout, reduces the sizes of
>> its media elements and otherwise improves the page load time and user
>> experience for mobile."
>> Mobile: "A Theme that is designed to be used only on mobile devices."
>>
>>  Notice I left adaptive off of the list, and I'm open to leaving mobile
>> off too if its not needed.
>>
>>
>> On Thu, Aug 22, 2013 at 7:27 PM, Emil Uzelac <emil at uzelac.me> wrote:
>>
>> mobile-responsive and that includes both?
>>  On Aug 22, 2013 5:46 PM, "Emil Uzelac" <emil at uzelac.me> wrote:
>>
>> Whatever is better. :-)
>> On Aug 22, 2013 5:44 PM, "Chip Bennett" <chip at chipbennett.net> wrote:
>>
>> Remember: those tags are, primarily, for *users* rather than for
>> developers. To the end user: what's the tangible difference between
>> "responsive" and "adaptive"? In this case, "end user" could be both the
>> site owner (the one who chooses and installs the Theme) or the site visitor
>> (who would view the website via devices with various screen sizes).
>>
>>  Do a developer, I agree 100% that the two terms have tangible,
>> meaningful differences.
>>
>>  I'm just struggling to see how a user would see any difference
>> whatsoever. In both cases, the Theme is designed to work on devices with
>> variously small screen sizes.
>>
>>
>> On Thu, Aug 22, 2013 at 3:34 PM, Josh Pollock <jpollock412 at gmail.com>wrote:
>>
>> I agree and disagree with Chip. I agree we need to find the definition
>> that is most useful to end users and two tags with the same definition is
>> probably confusing. The problem is some end users are more sophisticated
>> than others. Some know what responsive means, some don't. That said, we
>> shouldn't equate the two, because they are different. GIve me a little time
>> and I will propose some new definitions.
>>
>>  @Ulrich We can't just add tags to the guidelines. They need to be
>> supported by core. As part of the THX38 project this will most likely
>> happening. I'm hoping to go to the next THX38 meeting with a list of tags
>> that we, as theme reviewers, want added and feel like we can review
>> properly.
>>
>>
>> On Thu, Aug 22, 2013 at 3:17 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>
>> I'm one of those people who doesn't know the difference between
>> "responsive" and "adaptive". Well, until just now, because I googled it<http://www.techrepublic.com/blog/web-designer/what-is-the-difference-between-responsive-vs-adaptive-web-design/>.
>>
>>
>>  The TL;DR of that article:
>>
>>
>
> _______________________________________________
> theme-reviewers mailing listtheme-reviewers at lists.wordpress.orghttp://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/20130823/813f932b/attachment-0001.html>