Custom Image Header support *only* supports one header image, if it supported multiple images then I could see annexing "custom logos" into being supported with Custom Image Header ... actually I would likely start siding with Custom Image Header as a requirement if by default core code supported multiple images in the "header" area, otherwise I still believe it needs more work.<br>
<br>Custom Post Type Index may not really apply to the Theme repository but it should be recognized in a similar fashion as you noted.<br><br>If I am understanding things correctly, Admin bar will be public facing (for admins) themes may need to take that into account, it should be reviewed as such ... <br>
<br>We need one thread to discuss all of these items ... or better yet, one blog post.<br><br>"Upsell" themes need to be defined; simply and concisely, in everyday language. Then we need to sort out what is allowable and what will not be.<br>
<br><br>Cais.<br><br><div class="gmail_quote">On Thu, Nov 11, 2010 at 5:51 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</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;">
Post Formats, we've got a good start on.<div><br></div><div>Custom Post Type Index Pages: not really applicable to publicly-released Themes. I would treat similar to the "page-foobar.php" template files: if used, provide Theme Documentation explaining their use.</div>
<div><br></div><div>Admin Bar: I'm struggling to see how that fits into Theme Review Guidelines?</div><div><br></div><div>We've got several other things we need to hammer out, too - things that aren't specific to Version 3.1, but that have been held until the Version 3.1 update to the Guidelines (as summarized in my three-point proposal in the thread below).</div>
<div><br></div><div>I would like to add handling of Custom Image Header functionality to the discussion, too. I think "custom logo" functionality falls under "Custom Image Header" functionality, and if so, we need to clarify its usage.</div>
<div><br></div><div>Similarly, we need to discuss any special considerations for "upsell" Themes.</div><div><br></div><div><font color="#888888">Chip</font><div><div></div><div class="h5"><br><br><div class="gmail_quote">
On Thu, Nov 11, 2010 at 4:37 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 agree we need to get to work on 3.1 related Theme Review guidelines and changes to some of the individual items, but from the "master list" link below I am only really seeing a few items that need to be immediately addressed with the release of 3.1:<br>
<ul><li> <a href="http://codex.wordpress.org/Post_Formats" title="Post Formats" target="_blank">Post Formats</a> <a href="http://core.trac.wordpress.org/ticket/14746" title="http://core.trac.wordpress.org/ticket/14746" target="_blank">14746</a></li>
<li> Custom post Type Index Pages <a href="http://core.trac.wordpress.org/ticket/13818" title="http://core.trac.wordpress.org/ticket/13818" target="_blank">13818</a></li><li>Admin Bar <a href="http://core.trac.wordpress.org/ticket/14772" title="http://core.trac.wordpress.org/ticket/14772" target="_blank">14772</a></li>
</ul>I re-ordered them in the priority I see as related to the Theme Review guidelines.<br><br><br>Cais.<br><br><div class="gmail_quote"><div><div></div><div>On Thu, Nov 11, 2010 at 4:34 PM, 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: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div>By the way: <a href="http://wpdevel.wordpress.com/version-3-1-project-schedule/" target="_blank">WP 3.1 beta is scheduled for November 15th</a>, so we really need to hit version-specific changes hard in our next meeting.<div>
<br></div><div><font color="#888888">
Chip<br><br></font><div class="gmail_quote"><div>On Fri, Nov 5, 2010 at 1:39 PM, 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: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><br></div><div>By the way, here's the <a href="http://codex.wordpress.org/Version_3.1" target="_blank">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><font color="#888888">Chip</font></div></blockquote></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>
<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>