<div dir="ltr">I agree with Chip 100% +1 for "responsive"<div><br></div><div><a href="http://www.signalfire.us/mobile-friendly-vs-mobile-optimized-vs-responsive-design/">http://www.signalfire.us/mobile-friendly-vs-mobile-optimized-vs-responsive-design/</a><br>
</div><div><br></div><div>Big difference between them.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 22, 2013 at 2:34 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" 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 class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 22, 2013 at 3:17 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" 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 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><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><span style="font-size:13px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:20px">The distilled definition of a responsive web design is that it will </span><em style="font-size:13px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:20px"><b>fluidly change and respond</b></em><span style="font-size:13px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;line-height:20px"><b> to fit any screen or device size</b>.</span></div>
<div><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:20px"><br></span></div><div><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:20px">The condensed definition of an adaptive design is that it </span><em style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:20px"><b>will change to fit a predetermined set of screen and device sizes</b></em><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,Arial,sans-serif;font-size:13px;line-height:20px">.</span></div>
</blockquote><div><br></div><div>From a user perspective, I see no benefit gained from differentiating between the two. One is fluid; the other adjusts to predetermined intermediate sizes.</div><div><br></div><div>I would prefer to choose *one* term, e.g. "responsive", to apply to both design implementations. But, we should choose the term that is most meaningful/relevant to *users*. If "mobile-friendly" resonates more with users, let's use that one. If "responsive", then let's use that.</div>
<div><br></div><div>Then, having selected a term, create a meaningful definition that captures both design implementations, such as: "layout changes to fit various screen sizes".</div></div><div>
<div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Aug 22, 2013 at 3:10 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">If we are going to get into potential Responsive and Adaptive tags, which we should I'd like to add a few things:<div>I agree flex-width does not equal responsive.</div><div>The thing about responsive and adaptive tags is no one knows the difference between the two and those who do are probably not those who we are trying to help with these tags. I'm wondering if we should have two tags per definition. IE if you qualify for "responsive", you also qualify for "mobile-friendly", and if you qualify for "adaptive" you also qualify for "mobile-optimized." I think the mobile-friendly and mobile-adaptive tags would be more useful to most end users that are less interested in a nerdish need of nerds, <b>like me</b>, to categorize according to the "correct term".</div>
<div><br></div><div>So I'd like to propose that we call responsive/ mobile-friendly "A theme with a layout that employs a fluid grid system that changes in response to screen size." and adaptive/ mobile-optimized: "A theme with that adapts its layout and functionality based on screen size and device type in order to optimize display and performance on mobile devices."</div>
<div><br></div><div>Is there a need to add a "mobile" tag for themes designed to be used only on mobile devices? I'm really not sure.</div><div><br></div><div><br></div></div><div><div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">On Thu, Aug 22, 2013 at 2:25 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Big +1 for accessibility-ready. <div><br></div><div>Chip is correct flex-width is not the same as Responsive or Adaptive. </div><div><br></div><div>What @Konstantin noted yesterday about the tag being left from </div>
<div>WPCOM made me look over there again and maybe just maybe </div><div>we can copy what they have: "Responsive Layout"</div><div><br></div><div><a href="http://i.imgur.com/KsqXF01.png" target="_blank">http://i.imgur.com/KsqXF01.png</a><br>
</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 22, 2013 at 1:09 PM, Ulrich Pogson <span dir="ltr"><<a href="mailto:grapplerulrich@gmail.com" target="_blank">grapplerulrich@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Amy, you are right. If this was added to the Theme-Check it would make life easier for us.</div><div>
<br></div><div>Here is the GitHub link if anyone is intrested. <a href="https://github.com/Pross/theme-check" target="_blank">https://github.com/Pross/theme-check</a></div>
<div><br></div><div>I have added Chip's comments to the table here. I still need feedback on "microformats" tag.</div><div><br></div><a href="https://docs.google.com/spreadsheet/ccc?key=0AgFnu461m-SOdFlwS0cwWXVyRkJKeHVvY3pJbTIzc3c&usp=sharing" target="_blank">https://docs.google.com/spreadsheet/ccc?key=0AgFnu461m-SOdFlwS0cwWXVyRkJKeHVvY3pJbTIzc3c&usp=sharing</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On 22 August 2013 19:23, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><span style="color:rgb(80,0,80)">think that support for even a single post format (e.g. a Gallery Theme) is valid here.</span><br>
<blockquote><div>It depends if you count the default post format or not?</div></blockquote></div></blockquote><div><br></div></div><div>The "default" post format (i.e. "standard") is not actually a post format. There is no "default" or "standard" term defined for the post_format taxonomy. It is merely the fallback if no post format is defined. </div>
<div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><blockquote><div><div><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
(Note: "Text Domain" header tag is not used and not required; it is information-only, and optional.) </blockquote> <br></div>It is used for translating the theme description and page template page. See this <a href="https://foxnet-themes.fi/2013/07/02/translating-custom-page-template-names/" target="_blank"><span></span><span></span>article</a>. Responsive has the page templates translated in German if any one wants to test it.</div>
</blockquote></div></blockquote><div><br></div></div><div>Huh; you learn something new every day!</div><div><br></div><div>(Otto/Pross: should this be added to Theme Check, as a corollary test for add_theme_textdomain()?) </div>
</div></div></div>
<br></div></div><div>_______________________________________________<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></div></blockquote></div><br></div>
<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><br></div>
</div></div><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><br></div>
</div></div><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><br></div>
</div></div><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><br></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><br></div>