[theme-reviewers] Supporting Repo Child Themes

Chip Bennett chip at chipbennett.net
Thu Jun 6 15:02:09 UTC 2013


For the vast majority of Child Themes, I would recommend forking (i.e.
option #2).


On Thu, Jun 6, 2013 at 11:00 AM, esmi at quirm dot net <esmi at quirm.net>wrote:

> (Also posted to the forum support list)
>
> Generally speaking, when someone wants to make changes to a theme
> downloaded from wordpress.org, we recommend that they create a child
> theme or use a custom CSS plugin to avoid losing their customisations when
> they update the main theme.
>
> However, we're starting to see people using child themes downloaded from
> the Theme Repository and, in some cases, wanting to customise these child
> themes. Assuming that updated child themes in the Repo will generate the
> same update notices in the user's site, what would be the best practice
> suggestion in these cases?
>
> 1. Customise the child theme but keep a local backup copy of all changes?
>
> 2. Create a new child theme by copying the downloaded child, renaming it
> and then amending the new copy?
>
> 3. Something else entirely?
>
> Mel
> --
> http://quirm.net
> http://blackwidows.co.uk
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130606/ad3f1b22/attachment.html>


More information about the theme-reviewers mailing list