<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Make WordPress Themes &#187; Child-Theme</title>
	<atom:link href="http://make.wordpress.org/themes/tag/child-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://make.wordpress.org/themes</link>
	<description>Just another make.wordpress.org site</description>
	<lastBuildDate>Tue, 30 Apr 2013 11:53:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta3-24290</generator>
	<atom:link rel='hub' href='http://make.wordpress.org/themes/?pushpress=hub'/>
		<item>
		<title>Child Theme Support</title>
		<link>http://make.wordpress.org/themes/2013/02/15/child-theme-support/</link>
		<comments>http://make.wordpress.org/themes/2013/02/15/child-theme-support/#comments</comments>
		<pubDate>Fri, 15 Feb 2013 15:26:40 +0000</pubDate>
		<dc:creator>Chip Bennett</dc:creator>
				<category><![CDATA[discussion]]></category>
		<category><![CDATA[Child-Theme]]></category>
		<category><![CDATA[Child-Themes]]></category>
		<category><![CDATA[Guidelines]]></category>

		<guid isPermaLink="false">http://make.wordpress.org/themes/?p=1123</guid>
		<description><![CDATA[I have just added a draft section to the Theme Review Guidelines, to cover requirements for Child Theme support/facilitation for hosted Themes: &#160; Themes are required to facilitate the use of Child Themes. A &#8220;basic&#8221; Child Theme (i.e. a style.css with Template header tag and @import() of the Template style.css), when activated, should function exactly as the Theme itself functions. Themes are required to include functional and [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>I have just added <a href="http://codex.wordpress.org/Theme_Review#Child_Theme_Support">a draft section to the Theme Review Guidelines, to cover requirements for Child Theme support/facilitation</a> for hosted Themes:</p>
<p>&nbsp;</p>
<blockquote>
<ul>
<li>Themes are <b>required</b> to facilitate the use of <a title="Child Themes" href="http://codex.wordpress.org/Child_Themes">Child Themes</a>. A &#8220;basic&#8221; Child Theme (i.e. a <tt>style.css</tt> with <tt>Template</tt> header tag and <tt>@import()</tt> of the Template <tt>style.css</tt>), when activated, should function exactly as the Theme itself functions.</li>
<li>Themes are <b>required</b> to include functional and resource files in a manner that facilitates the use of Child Themes:
<ul>
<li>Use <tt><a title="Function Reference/get template directory uri" href="http://codex.wordpress.org/Function_Reference/get_template_directory_uri">get_template_directory_uri()</a></tt> to include functional files, or resources that <i>are not intended</i> to be included in/over-ridden the Child Theme.</li>
<li>Use <tt><a title="Function Reference/get stylesheet directory uri" href="http://codex.wordpress.org/Function_Reference/get_stylesheet_directory_uri">get_stylesheet_directory_uri()</a></tt> to include resources that <i>are intended</i> to be included in/over-ridden by the Child Theme.</li>
</ul>
</li>
</ul>
</blockquote>
<p>&nbsp;</p>
<p>Based on discussion on the mail-list, consensus appears to be that facilitating end user use of Child Themes is beneficial, so this discussion is the first step in incorporating Child Theme support into the Guidelines.</p>
<p>Please discuss. Do you agree/disagree that Child Theme support should be added to the Guidelines? Are the above Guidelines sufficient? What should be added/removed/changed? What about pluggable/filterable functions?</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/themes/2013/02/15/child-theme-support/feed/</wfw:commentRss>
		<slash:comments>23</slash:comments>
		</item>
		<item>
		<title>Child Themes will now be considered for inclusion&#8230;</title>
		<link>http://make.wordpress.org/themes/2011/04/09/child-themes-at-wordpress-extend/</link>
		<comments>http://make.wordpress.org/themes/2011/04/09/child-themes-at-wordpress-extend/#comments</comments>
		<pubDate>Sat, 09 Apr 2011 15:00:28 +0000</pubDate>
		<dc:creator>Edward Caissie</dc:creator>
				<category><![CDATA[status]]></category>
		<category><![CDATA[Child-Theme]]></category>
		<category><![CDATA[Child-Themes]]></category>
		<category><![CDATA[Guidelines]]></category>

		<guid isPermaLink="false">http://make.wordpress.org/themes/?p=213</guid>
		<description><![CDATA[Child-Themes will now be considered for inclusion into the WordPress Extend Themes repository. Note: Child Themes are not currently being considered for inclusion in WordPress Extend. Please be sure to read the Theme Review process and guidelines; also, please note the additional Child-Theme guidelines before submitting a Child-Theme for consideration. Please note, although at the [&#8230;]]]></description>
				<content:encoded><![CDATA[<p><strike><a href="http://codex.wordpress.org/Child_Themes">Child-Themes</a> will now be considered for inclusion into the WordPress Extend <a href="http://wordpress.org/extend/themes/">Themes repository</a>.</strike></p>
<p><ins>Note: Child Themes <em>are not currently being considered</em> for inclusion in WordPress Extend.</ins></p>
<p>Please be sure to read the <a title="Theme Review Process and Scope" href="http://make.wordpress.org/themes/about/theme-review-process-and-scope/">Theme Review</a> process and guidelines; also, please note the additional <a title="Discussion – Child Themes on the Repository – Guidelines" href="http://make.wordpress.org/themes/2011/01/24/discussion-child-themes-on-the-repository-guidelines/">Child-Theme</a> guidelines before submitting a Child-Theme for consideration.</p>
<p>Please note, although at the time of this writing the upload script may note the Child-Theme &#8220;fails&#8221; as the criteria used for Child-Themes is slightly different. If the Child-Theme did actually pass you would see at the bottom of the upload acknowledgement page a reference to the new Themes Trac ticket as well as receiving an email referencing the ticket as well.</p>
<p>You will also be able to check the open status of the Child-Theme in this Trac report: <a href="http://themes.trac.wordpress.org/report/6">http://themes.trac.wordpress.org/report/6</a></p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/themes/2011/04/09/child-themes-at-wordpress-extend/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Discussion &#8211; Child Themes on the Repository &#8211; Guidelines</title>
		<link>http://make.wordpress.org/themes/2011/01/24/discussion-child-themes-on-the-repository-guidelines/</link>
		<comments>http://make.wordpress.org/themes/2011/01/24/discussion-child-themes-on-the-repository-guidelines/#comments</comments>
		<pubDate>Mon, 24 Jan 2011 09:10:25 +0000</pubDate>
		<dc:creator>Frumph</dc:creator>
				<category><![CDATA[post]]></category>
		<category><![CDATA[Child-Theme]]></category>
		<category><![CDATA[discussion]]></category>
		<category><![CDATA[Guidelines]]></category>

		<guid isPermaLink="false">http://make.wordpress.org/themes/2011/01/24/discussion-child-themes-on-the-repository-guidelines/</guid>
		<description><![CDATA[1) Parent themes of child themes that are developed need to be made child-theme ready; proper use of where to find files with get_template_part, get_stylesheet_ and get_template_ functions. 2) http://codex.wordpress.org/Child_Themes documentation is applied as part of the theme review process when checking child themes, all information is to be considered good practice and required, with [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>1) Parent themes of child themes that are developed need to be made child-theme ready; proper use of where to find files with get_template_part, get_stylesheet_ and get_template_ functions.<br />
2) <a href="http://codex.wordpress.org/Child_Themes" rel="nofollow">http://codex.wordpress.org/Child_Themes</a> documentation is applied as part of the theme review process when checking child themes, all information is to be considered good practice and required, with addition to the theme review representation of license information.<br />
3) Parent themes of child themes submitted must have passed the current theme review guidelines for the current revision of WordPress, not if they have passed before, but specifically with the current revision of WordPress.<br />
4) Child themes are reviewed with the parent theme; must pass current theme review guidelines and associated child theme documentation.<br />
5) Recommendation to use the parent themes repository slug as the prefix to the child theme&#8217;s name.  ex. easel-highsociety,  atahualpa-wired, this is only the name of the theme &amp; directory name of theme in the zip, not where to find the theme; even as found in the <a href="http://codex.wordpress.org/Child_Themes" rel="nofollow">http://codex.wordpress.org/Child_Themes</a> being part of the review process, this naming convention will stay a recommendation; however, declared best-practice.<br />
6) Description in the style.css must clearly state that it is a child theme example: &#8220;This is a child theme for the Easel theme.&#8221; &#8211; This is for redundancy of recognition that it is a child theme, even though other things will be noted on the repository that it is a child theme, this is for the wp-admin -&gt; themes page for the end user.</p>
<p>Additional For Developers:<br />
1) It is the responsibility of the developer of child themes to keep their child themes up to date with the current revision of their theme that is updated.   If a developer make changes to the parent theme, it is the developers responsibility to keep the child themes updated as well.</p>
<p>Changes, word usage, additional guidelines and protocols, as well as information regarding use of child-theme tag requested as part of this discussion.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/themes/2011/01/24/discussion-child-themes-on-the-repository-guidelines/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
	</channel>
</rss>
