[theme-reviewers] Option to create child theme from theme option

Otto otto at ottodestruct.com
Wed Jan 22 17:30:06 UTC 2014


I'd say that the act of creating a child theme isn't theme-specific.
Other than the "Parent: whatever" bit being different in the created
style.css file, creating a child theme is definitely not theme
territory.

This falls down into that whole functionality argument, and IMO,
themes try to do too much. Adding all these features that modify how
the system works lead to user confusion.

While there is a valid argument that themes should be about more than
"just picking colors", there is also a reasonable argument that themes
should be about the "display" of the site. *Creating* a child theme
isn't really about display, it's about organization and maintenance.
You use the child theme to customize the look and feel of the parent,
but you actually create the child theme to allow the parent to be
updated without modifications. Two different things.

And realistically, child themes aren't something I think end-users
should be doing themselves anyway. There's better approaches that are
more user-friendly. Jetpack's Custom CSS feature demonstrates one
possible approach, where the CSS modifications can be entirely outside
the parent/child system.
-Otto


On Wed, Jan 22, 2014 at 9:11 AM, Chip Bennett <chip at chipbennett.net> wrote:
> At this point, it's just a discussion matter, not a settled issue.
>
> But looking at that functionality: wow, that would make a really awesome
> Plugin. It basically would let users create a Child Theme using the
> currently active Theme as its template (Parent Theme).
>
> IMHO, that's Plugin territory.
>
> And also: I really don't like the idea of asking Theme reviewers also to
> have to be Plugin reviewers.. I question whether it is reasonable to ask a
> *Theme* reviewer to have to understand not only the WordPress template
> system, but *also* the Filesystem API, in order to review that Theme
> properly? There are very few reviewers competent to conduct such a review
> (and while I'm pretty sure I could get through it, I would have to go back
> into the Filesystem API docs to be sure; it's certainly not inherent). Otto
> could conduct that review without research. Justin might be able to. A few
> others (who do both Plugin and Theme development) could. But the vast
> majority?
>
> Just my thoughts...
>
>
> On Wed, Jan 22, 2014 at 9:50 AM, Faishal Saiyed <saiyedfaishal at gmail.com>
> wrote:
>>
>> If "One-Click Child Themes" is plugin territory functionality then what
>> about the theme that already approved ?
>>
>> I am reviewing 16211 and following two are approved theme
>>
>>  https://themes.trac.wordpress.org/ticket/16209
>>  https://themes.trac.wordpress.org/ticket/16210
>>
>>
>> On Wed, Jan 22, 2014 at 12:59 AM, Faishal Saiyed <saiyedfaishal at gmail.com>
>> wrote:
>>>
>>> Hi,
>>>
>>> I am reviewing one theme and they give one section call "One-Click Child
>>> Themes" in theme option. using that setting i can create child theme by
>>> providing name.
>>>
>>> I will create that name directory in wp-content theme directory and
>>> create 3 files
>>> 1. style.css
>>> 2. screenshoot.png
>>> 3. function.php
>>>
>>> I feel like it is not part of presentation , it is a part of
>>> functionality.
>>>
>>> But i want other theme-reviewers suggestion on same.
>>>
>>>
>>> --
>>> Faishal Saiyed
>>> Web: about.me
>>
>>
>>
>>
>> --
>> Faishal Saiyed
>> Web: about.me
>>
>> _______________________________________________
>> 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
>


More information about the theme-reviewers mailing list