<font color="#333333" face="arial, helvetica, sans-serif">Either or should be all right.<br></font><div><font color="#333333" face="arial, helvetica, sans-serif"><br></font></div><div><font color="#333333" face="arial, helvetica, sans-serif">Emil<br>
</font><div><font color="#333333"><font size="2"><font face="arial,helvetica,sans-serif"><br></font></font></font></div><div><font color="#333333"><font size="2"><font face="arial,helvetica,sans-serif"><br clear="all"></font></font></font><div>
<strong><font face="arial, helvetica, sans-serif">----</font></strong></div><div><font face="arial, helvetica, sans-serif"><strong>Emil Uzelac</strong> | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E: <a href="mailto:emil@themeid.com" target="_blank">emil@themeid.com</a> | <a href="http://themeid.com/" target="_blank">http://themeid.com</a></font></div>
<div><font color="#999999" face="arial, helvetica, sans-serif">Make everything as simple as possible, but not simpler. - Albert Einstein</font></div><br>
<br><br><div class="gmail_quote">On Wed, Nov 30, 2011 at 5:16 PM, Justin Tadlock <span dir="ltr"><<a href="mailto:justin@justintadlock.com">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;">
<u></u>
<div bgcolor="#ffffff" text="#000000">
For the specific case I'm asking about, it would be a truly blank
theme with no CSS definitions. 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.
So, I'm definitely in favor of having a "blank" or "developer" tag
for such themes.<div><div class="h5"><br>
<br>
On 11/29/2011 3:14 PM, Chip Bennett wrote:
<blockquote 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"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></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>
<div><br>
<br>
<br>
<div class="gmail_quote">On Tue, Nov 29, 2011 at 3:37
PM, Ian Stewart <span dir="ltr"><<a href="mailto:ian@iandanielstewart.com" target="_blank">ian@iandanielstewart.com</a>></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>
> Well they're not really a special-use case
from the perspective of the<br>
> end user who wants to download a special kind
of (usable) theme for<br>
> WordPress. It seems that they warrant
perhaps their own separate<br>
> developer section outside of extend on the
site, or maybe just some<br>
> 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 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>
</div>
</div>
</blockquote>
</div>
<br>
</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>
<pre><fieldset></fieldset>
_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
</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></div>