[wp-docs] Theme Frameworks Codex Entry

[Chip Bennett]

What are you wanting to edit on that one? Please tread lightly; Theme
developers have been using that list for almost two years now as THE
"go-to" source for Theme Review requirements. Any content changes would
have a major impact to ongoing reviews.

Thanks,

Chip

On Wed, Mar 14, 2012 at 8:51 PM, Lorelle on WordPress <
lorelleonwordpress at gmail.com> wrote:

> Ah yes! Forgot I had that on my "MUST EDIT" list...the list is soooo long.
> Need more time in the day.
>
> LOL!
>
> That one is back up at the top of the list of fixing. Thanks!
>
> Lorelle
>
>
>
> On Wed, Mar 14, 2012 at 6:38 PM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> You mean, something other than this?
>> http://codex.wordpress.org/Theme_Review
>>
>> :)
>>
>> Chip
>>
>>
>> On Wed, Mar 14, 2012 at 8:31 PM, Lorelle on WordPress <
>> lorelleonwordpress at gmail.com> wrote:
>>
>>> Excellent.
>>>
>>> And on the point of the Theme Review Team, am I missing a doc that
>>> spells out all the details of how the Theme Review Team works and a
>>> checklist in the Codex? We really need something like that to guide people
>>> not just through the process (how do I get my Theme to the Review Team,
>>> update it, maintain it, support it...etc.) but gives a good list of what
>>> the team looks for and condemns in the review process.
>>>
>>> Thanks!!!
>>>
>>> Lorelle
>>>
>>>
>>>
>>> On Wed, Mar 14, 2012 at 1:00 PM, Chip Bennett <chip at chipbennett.net>wrote:
>>>
>>>> Most of those are on my list. :) It's a topic that occasionally comes
>>>> up for the Theme Review Team, so I want to make sure that the terminology
>>>> is consistent. See here for more:
>>>>
>>>> http://make.wordpress.org/themes/2012/03/14/theme-frameworks-and-namespacing-guidelines/
>>>>
>>>> PSD conversion is probably outside the scope, but if someone wants to
>>>> tackle an entry for that, it would be good to link from the Theme
>>>> Development entry.
>>>>
>>>> I'll take on as much as I can, and perhaps leave the last couple of
>>>> points to others who can speak to those aspects better than I can.
>>>>
>>>> Thanks,
>>>>
>>>> Chip
>>>>
>>>>
>>>> On Wed, Mar 14, 2012 at 12:52 PM, Lorelle on WordPress <
>>>> lorelleonwordpress at gmail.com> wrote:
>>>>
>>>>> That's been on my to do list for ages, so go for it.
>>>>>
>>>>> On my notes to expand the article include:
>>>>>
>>>>> * Better explanation and definition of framework.
>>>>> * Updating the list with free frameworks.
>>>>> * Explaining the difference between a framework and WordPress Theme.
>>>>> * A list of the code and features that could be in a framework.
>>>>> * How to treat it differently or the same as a Theme.
>>>>> * Why choose a framework over a Theme.
>>>>> * Can any Theme be a framework.
>>>>> * How to convert a PSD/Wireframe to framework (possibly new article or
>>>>> reference point)
>>>>> * How to Child Theme a Framework (it's a little different as you are
>>>>> adding all the styles not just changing specific styles)
>>>>> * Thoughts/Suggestions/Tips/Techniques for creating a Framework in
>>>>> WordPress (in other words - while it can "do it all" maybe it shouldn't).
>>>>>
>>>>> Not sure you want to take all that on, Chip, but that's on my list if
>>>>> anyone else wants to pitch in.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Lorelle
>>>>>
>>>>>
>>>>> On Wed, Mar 14, 2012 at 10:15 AM, Chip Bennett <chip at chipbennett.net>wrote:
>>>>>
>>>>>> Does anyone have a problem with me making some changes to this entry?
>>>>>> http://codex.wordpress.org/Theme_Frameworks
>>>>>>
>>>>>> I would like to revise, to clarify between Theme framework as
>>>>>> "drop-in code library" and Theme framework as "stand-alone base/starter
>>>>>> Theme".
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Chip
>>>>>>
>>>>>> _______________________________________________
>>>>>> wp-docs mailing list
>>>>>> wp-docs at lists.automattic.com
>>>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> wp-docs mailing list
>>>>> wp-docs at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> wp-docs mailing list
>>>> wp-docs at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>>
>>>>
>>>
>>> _______________________________________________
>>> wp-docs mailing list
>>> wp-docs at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>>
>>>
>>
>> _______________________________________________
>> wp-docs mailing list
>> wp-docs at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-docs
>>
>>
>
> _______________________________________________
> wp-docs mailing list
> wp-docs at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-docs/attachments/20120314/a640e103/attachment-0001.htm>