Love it!<div><br></div><div>I would propose adding it to OPTIONAL WordPress features initially, until we get a handle on how quickly and how widespread Post Formats become. Of course, as with RECOMMENDED features, implementation itself is not required, but if the feature is implemented, it is REQUIRED to be implemented properly.</div>
<div><br></div><div>That will mean that current Themes that provide custom loops for "Gallery" and "Asides" categories (<a href="http://codex.wordpress.org/Post_Formats">or any of the standard post formats</a>) will need to migrate to use of Post Formats, while optionally providing backward-compatibility to the current implementation.</div>
<div><br></div><div>By the way, here's the <a href="http://codex.wordpress.org/Version_3.1">master list of major 3.1 changes</a>. Anything else in there we should be considering?</div><div><br></div><div>As for other Guidelines changes for 3.1, I would add the following proposals:</div>
<div><br></div><div>1) Everything currently marked as "draft" in the Guidelines</div><div>2) Use of "License"/"License URI" header tags increases in criticality from *recommended* to *required*</div>
<div>3) Use of TimThumb prohibited (*required* not to use, even for backward compatibility). If we go this route, I will volunteer to put together a tutorial for how to migrate TimThumb-generated images using custom fields over to the WordPress media manager. </div>
<div><br></div><div>Additional changes to the Theme Review Codex page: </div><div><br></div><div>1) Once we are up and running on our WPORG site, I propose that we move all non-Guideline information (e.g. Process, Scope, How to Become a Theme Reviewer) over to the WPORG site. (Perhaps leave the "Resources" section, as it has links to various Theme check/validation tools.)</div>
<div>2) Re-write the Guidelines so that we have a condensed list of the Guidelines in principle, with intra-page links to expanded/detailed information about each Guideline (as per the mail-list discussion from a couple weeks ago).</div>
<div><br></div><div>Anything else?</div><div><br></div><div>Just as an FYI: WP 3.1 is scheduled for a December release, so we need to get any version-specific Guidelines revisions up as soon as possible. I would want to shoot for having the version-specific changes published at or around the time of the first beta release of 3.1.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 8:05 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
This is a great idea for WP3.1 Theme recommendations. Thanks!<br><br><br>Cais.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 4:53 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.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">Future suggestion, just starting discussion now.<br>
<br>
<a href="http://wpdevel.wordpress.com/2010/11/05/post-formats-in-core/" target="_blank">http://wpdevel.wordpress.com/2010/11/05/post-formats-in-core/</a><br>
<br>
Post formats are a new thing that will be in 3.1. Basic idea is to<br>
provide a specific method for specifying the "format" of a post, for<br>
display. This is to replace the usage of categories for much the same<br>
thing.<br>
<br>
Example: Asides. In the past, it's often been suggested to make an<br>
"asides" category, and then posts can be put into that category and<br>
displayed differently based on either styling rules from post_class()<br>
or from in_category('asides').<br>
<br>
This new approach allows a theme to define a set of post formats like so:<br>
add_theme_support( 'post-formats', array( 'aside', 'gallery', 'whatever' ) );<br>
<br>
And then the post format can be selected when saving the post. A<br>
function call of "get_post_format( $post->ID )" can be used to<br>
determine the format, and post_class() will also create<br>
"format-whatever" classes, for pure-css styling.<br>
<br>
So, recommendation for future themes (post-3.1): Do not use categories<br>
for displaying posts differently. Instead, support post-formats.<br>
<font color="#888888"><br>
-Otto<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>
</font></blockquote></div><br>
</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>