[theme-reviewers] Post formats

[Edward Caissie]

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.

Custom Post Type Index may not really apply to the Theme repository but it
should be recognized in a similar fashion as you noted.

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 ...

We need one thread to discuss all of these items ... or better yet, one blog
post.

"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.


Cais.

On Thu, Nov 11, 2010 at 5:51 PM, Chip Bennett <chip at chipbennett.net> wrote:

> Post Formats, we've got a good start on.
>
> 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.
>
> Admin Bar: I'm struggling to see how that fits into Theme Review
> Guidelines?
>
> 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).
>
> 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.
>
> Similarly, we need to discuss any special considerations for "upsell"
> Themes.
>
> Chip
>
>
> On Thu, Nov 11, 2010 at 4:37 PM, Edward Caissie <edward.caissie at gmail.com>wrote:
>
>> 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:
>>
>>    - Post Formats <http://codex.wordpress.org/Post_Formats> 14746<http://core.trac.wordpress.org/ticket/14746>
>>    - Custom post Type Index Pages 13818<http://core.trac.wordpress.org/ticket/13818>
>>    - Admin Bar 14772 <http://core.trac.wordpress.org/ticket/14772>
>>
>> I re-ordered them in the priority I see as related to the Theme Review
>> guidelines.
>>
>>
>> Cais.
>>
>> On Thu, Nov 11, 2010 at 4:34 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>
>>> By the way: WP 3.1 beta is scheduled for November 15th<http://wpdevel.wordpress.com/version-3-1-project-schedule/>,
>>> so we really need to hit version-specific changes hard in our next meeting.
>>>
>>> Chip
>>>
>>> On Fri, Nov 5, 2010 at 1:39 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>>
>>>>
>>>> By the way, here's the master list of major 3.1 changes<http://codex.wordpress.org/Version_3.1>.
>>>> Anything else in there we should be considering?
>>>>
>>>> As for other Guidelines changes for 3.1, I would add the following
>>>> proposals:
>>>>
>>>> 1) Everything currently marked as "draft" in the Guidelines
>>>> 2) Use of "License"/"License URI" header tags increases in criticality
>>>> from *recommended* to *required*
>>>> 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.
>>>>
>>>> Additional changes to the Theme Review Codex page:
>>>>
>>>> 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.)
>>>> 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).
>>>>
>>>> Anything else?
>>>>
>>>> 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.
>>>>
>>>> Chip
>>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20101111/59c8e5d3/attachment.htm>