<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    For the specific case I'm asking about, it would be a truly blank
    theme with no CSS definitions.&nbsp; It definitely wouldn't pass all the
    unit test guidelines.<br>
    <br>
    Honestly, I'd rather Average Joe *not* download and try to use it
    unless, of course, he's wanting to learn about theme development.&nbsp;
    So, I'm definitely in favor of having a "blank" or "developer" tag
    for such themes.<br>
    <br>
    On 11/29/2011 3:14 PM, Chip Bennett wrote:
    <blockquote
cite="mid:CAPdLKqc-LNFVQHWBYA=m2JTHXh8OX6QfoKz8Lnb6G9Bh=jzH-A@mail.gmail.com"
      type="cite">The reason I see it as a "niche" or "special use" case
      is that, 99.99% of the time, end users are not going to use a
      truly "blank" (i.e. NO CSS definitions, whatsoever) on a live
      site, without modification, and such use is not the intended
      purpose of such Themes.
      <div>
        <br>
      </div>
      <div>Chip<br>
        <br>
        <div class="gmail_quote">On Tue, Nov 29, 2011 at 3:01 PM, Edward
          Caissie <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            I do not have any issues with a "blank" theme, generally
            speaking I would consider most "minimalist" themes as
            working to be considered along the lines of "blank" as well
            ... at least given definition I would use when reading
            "minimalist".<br>
            <br>
            Having another theme in the repository specifically, or at
            least originally, designed for the purpose of helping new
            (or old) "developers" is a great idea. I'm not even really
            seeing it requiring a niche label as I am taking from the
            original premise it would pass the standard guideline
            requirements as one of its initial goals.<br>
            <br>
            <br clear="all">
            Cais.
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
                <br>
                <div class="gmail_quote">On Tue, Nov 29, 2011 at 3:37
                  PM, Ian Stewart <span dir="ltr">&lt;<a
                      moz-do-not-send="true"
                      href="mailto:ian@iandanielstewart.com"
                      target="_blank">ian@iandanielstewart.com</a>&gt;</span>
                  wrote:<br>
                  <blockquote class="gmail_quote" style="margin: 0pt 0pt
                    0pt 0.8ex; border-left: 1px solid rgb(204, 204,
                    204); padding-left: 1ex;">
                    <div>On 2011-11-29, at 2:11 PM, Angelo Bertolli
                      wrote:<br>
                      <br>
                      &gt; Well they're not really a special-use case
                      from the perspective of the<br>
                      &gt; end user who wants to download a special kind
                      of (usable) theme for<br>
                      &gt; WordPress. &nbsp;It seems that they warrant
                      perhaps their own separate<br>
                      &gt; developer section outside of extend on the
                      site, or maybe just some<br>
                      &gt; links from the wiki.<br>
                      <br>
                    </div>
                    I think separating them out would be OK but I think
                    labelling them as "blank" would be better than
                    "developer". It's friendlier to people who wouldn't
                    label themselves as developers but are more than
                    capable of hacking a blank theme.<br>
                    <span><font color="#888888"><br>
                        Ian<br>
                      </font></span>
                    <div>
                      <div>_______________________________________________<br>
                        theme-reviewers mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:theme-reviewers@lists.wordpress.org"
                          target="_blank">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>
                      </div>
                    </div>
                  </blockquote>
                </div>
                <br>
              </div>
            </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>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>
  </body>
</html>