<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I actually like those top-level categories from ThemeForest. Users
are probably more likely to look for an "e-commerce" theme rather
than a "blue" theme. Or, better yet, they could search for a "blue"
+ "e-commerce" theme, which just instantly makes searching themes
more useful.<br>
<br>
Also, I think we should propose dropping the "threaded-comments"
tag. All themes are required to support this now, so this offers no
real benefit.<br>
<br>
<div class="moz-cite-prefix">On 8/22/2013 11:34 PM, Josh Pollock
wrote:<br>
</div>
<blockquote
cite="mid:CAHVkt5n2uNPGPg4W4Sm1sH2BdsVGvZb-RwC=1ZoqSuLPEPmVfA@mail.gmail.com"
type="cite">
<div dir="ltr">@justin agreed.
<div><br>
</div>
<div>We ned to think about more than just mobile/responsive/etc
tags.</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>@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.</div>
<div>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."</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Aug 23, 2013 at 12:16 AM,
Justin Tadlock <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:justin@justintadlock.com" target="_blank">justin@justintadlock.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> 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.<br>
<br>
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.<br>
<br>
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.
<div>
<div class="h5"><br>
<br>
<div>On 8/22/2013 10:52 PM, Josh Pollock wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">@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.
<div><br>
</div>
<div>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?
<div> <br>
</div>
<div>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 <span></span>bringing own ideas.<br>
<br>
On Thursday, August 22, 2013, Chip Bennett
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">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.
<div> <br>
</div>
<div>IMHO, the tag list could probably stand
for a bit of an overhaul - but that would
be a bigger discussion than this one.</div>
</div>
<div><br>
<br>
<div>On Thu, Aug 22, 2013 at 8:27 PM, Josh
Pollock <span dir="ltr"><<a
moz-do-not-send="true">jpollock412@gmail.com</a>></span>
wrote:<br>
<blockquote style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">How about this:
<div><br>
</div>
<div>Responsive: "<span
style="font-family:arial,sans-serif;font-size:13px">A
theme with a layout that employs a
fluid grid system that changes in
response to screen size."</span></div>
<div><span
style="font-family:arial,sans-serif;font-size:13px">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."</span></div>
<div><span
style="font-family:arial,sans-serif;font-size:13px">Mobile:
"A Theme that is designed to be
used only on mobile devices."</span></div>
<div><span
style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span
style="font-family:arial,sans-serif;font-size:13px">Notice
I left adaptive off of the list,
and I'm open to leaving mobile off
too if its not needed.</span></div>
</div>
<div>
<div>
<div> <br>
<br>
<div>On Thu, Aug 22, 2013 at 7:27
PM, Emil Uzelac <span dir="ltr"><<a
moz-do-not-send="true">emil@uzelac.me</a>></span>
wrote:<br>
<blockquote style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<p dir="ltr">mobile-responsive
and that includes both?</p>
<div>
<div>
<div>On Aug 22, 2013 5:46
PM, "Emil Uzelac" <<a
moz-do-not-send="true">emil@uzelac.me</a>>
wrote:<br
type="attribution">
<blockquote
style="margin:0 0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<p dir="ltr">Whatever
is better. :-)</p>
<div>On Aug 22, 2013
5:44 PM, "Chip
Bennett" <<a
moz-do-not-send="true">chip@chipbennett.net</a>>
wrote:<br
type="attribution">
<blockquote
style="margin:0 0
0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<div dir="ltr">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).
<div> <br>
</div>
<div>Do a
developer, I
agree 100%
that the two
terms have
tangible,
meaningful
differences.</div>
<div><br>
</div>
<div>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.</div>
</div>
<div><br>
<br>
<div>On Thu, Aug
22, 2013 at
3:34 PM, Josh
Pollock <span
dir="ltr"><<a
moz-do-not-send="true">jpollock412@gmail.com</a>></span> wrote:<br>
<blockquote
style="margin:0
0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<div dir="ltr">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.
<div> <br>
</div>
<div>@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.</div>
</div>
<div>
<div>
<div><br>
<br>
<div>On Thu,
Aug 22, 2013
at 3:17 PM,
Chip Bennett <span
dir="ltr"><<a
moz-do-not-send="true">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote
style="margin:0
0 0
.8ex;border-left:1px
#ccc
solid;padding-left:1ex">
<div dir="ltr">I'm
one of those
people who
doesn't know
the difference
between
"responsive"
and
"adaptive".
Well, <a
moz-do-not-send="true"
href="http://www.techrepublic.com/blog/web-designer/what-is-the-difference-between-responsive-vs-adaptive-web-design/"
target="_blank">until just now, because I googled it</a>.
<div> <br>
</div>
<div>The TL;DR
of that
article:</div>
<div><br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<div class="im">
<pre>_______________________________________________
theme-reviewers mailing list
<a moz-do-not-send="true" href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a moz-do-not-send="true" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</div>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a moz-do-not-send="true"
href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a moz-do-not-send="true"
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
theme-reviewers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a>
<a class="moz-txt-link-freetext" href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</body>
</html>