[theme-reviewers] Carrington Framework / Carrington Text
edward.caissie at gmail.com
Thu Sep 2 16:09:41 UTC 2010
True, but what I am suggesting as a new thread is "Frameworks in General",
the title of this thread would imply Carrington related items more so than
On Thu, Sep 2, 2010 at 12:03 PM, Chip Bennett <chip at chipbennett.net> wrote:
> I don't see it as a derailment of the thread. The framework-core
> consideration is the primary reason why I asked for help in the first place.
> On Thu, Sep 2, 2010 at 10:53 AM, Edward Caissie <edward.caissie at gmail.com>wrote:
>> True ... and not wanting to de-rail this thread any further (*grin*) ...
>> this is potentially a (new) discussion thread that could be on par with
>> child-themes as it is very closely related as I see it.
>> On Thu, Sep 2, 2010 at 11:50 AM, Chip Bennett <chip at chipbennett.net>wrote:
>>> On Thu, Sep 2, 2010 at 10:42 AM, Edward Caissie <
>>> edward.caissie at gmail.com> wrote:
>>>> Thanks Chris ...
>>>> "Framework" themes are a whole different animal than most themes ... and
>>>> some tend to do things out of the ordinary.
>>>> I'll post some questions, here:
>>>> - Should they be handled differently?
>>>> - Should we add additonal Trac keywords?
>>>> - Should there be an assignable tag by the Review team so they
>>>> enter/exist in the repository with more recognition of their inherent
>>>> potential and options?
>>>> Just some thoughts, there are perhaps 10 or so that would come to mind
>>>> if we took a look at the repository ... the Carrington themes, Thematic,
>>>> Hybrid, ComicPress, Suffusion, Atahualpa, Tarski, etc come to mind off the
>>>> top of my head, I know there are more.
>>>> "Framework" may not be the most appropriate term, but these themes et
>>>> al. represent the ones that have a great many available options, for
>>>> example, that are well above and beyond most.
>>> I would go with Justin Tadlock's nomenclature with respect to
>>> "frameworks" - that is, drop-in code on top of which Parent Themes are
>>> built. In Carrington's case, this drop-in code is "Carrington Core". I
>>> believe Thematic and Hybrid are (or will be?) much the same.
>>> My thinking is that we really need first to review/approve the framework
>>> code. That way, if a Theme is using a known/approved version of the
>>> framework, that part can be ignored in the Theme review.
>>> The question then becomes: how best to handle review/approval of
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers