<?xml version="1.0" encoding="UTF-8"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>ThemeShaper Forums Topic: it is important to make a child theme???? cant we work on thematic directly</title>
<link>http://themeshaper.com/forums/</link>
<description>Help In Shaping WordPress Themes</description>
<language>en</language>
<pubDate>Wed, 22 May 2013 10:44:36 +0000</pubDate>

<item>
<title>Jonny Janiero on "it is important to make a child theme???? cant we work on thematic directly"</title>
<link>http://themeshaper.com/forums/topic/it-is-important-to-make-a-child-theme-cant-we-work-on-thematic-directly#post-18175</link>
<pubDate>Fri, 07 Jan 2011 22:12:21 +0000</pubDate>
<dc:creator>Jonny Janiero</dc:creator>
<guid isPermaLink="false">18175@http://themeshaper.com/forums/</guid>
<description>&#60;p&#62;its works pretty much the same as if you started hacking core WordPress files. a new version drops, hacks are lost. thats why people started using hooks and filters to ammend WordPress core (over direct hacks).&#60;br /&#62;
so, a child themes relationship to its parent is the same relationship as WordPress to a parent theme.&#60;br /&#62;
many have argued that child themes add bloat and confusion.&#60;br /&#62;
its just a safe extesion really. pretty much like having a super duper plugin that controls php and css.
&#60;/p&#62;</description>
</item>
<item>
<title>xxxevilgrinxxx on "it is important to make a child theme???? cant we work on thematic directly"</title>
<link>http://themeshaper.com/forums/topic/it-is-important-to-make-a-child-theme-cant-we-work-on-thematic-directly#post-18168</link>
<pubDate>Fri, 07 Jan 2011 17:41:45 +0000</pubDate>
<dc:creator>xxxevilgrinxxx</dc:creator>
<guid isPermaLink="false">18168@http://themeshaper.com/forums/</guid>
<description>&#60;p&#62;Agreed. Child themes used to confuse me at first but after a while of NEVER having to rehack your theme to pieces because of an upgrade, or - gasp! - opting not to upgrade! -  I'd never go back to the old method. Child themes are much simpler.
&#60;/p&#62;</description>
</item>
<item>
<title>nickbernier on "it is important to make a child theme???? cant we work on thematic directly"</title>
<link>http://themeshaper.com/forums/topic/it-is-important-to-make-a-child-theme-cant-we-work-on-thematic-directly#post-18163</link>
<pubDate>Fri, 07 Jan 2011 12:34:22 +0000</pubDate>
<dc:creator>nickbernier</dc:creator>
<guid isPermaLink="false">18163@http://themeshaper.com/forums/</guid>
<description>&#60;p&#62;The main reason you want to make a child theme is to ensure that you can update/upgrade your base Thematic without having to track all the changes you had made in its cores files and then have to go back and redo it all.&#60;/p&#62;
&#60;p&#62;To me, that's the main reason why I've stuck to the child themes.
&#60;/p&#62;</description>
</item>
<item>
<title>renz on "it is important to make a child theme???? cant we work on thematic directly"</title>
<link>http://themeshaper.com/forums/topic/it-is-important-to-make-a-child-theme-cant-we-work-on-thematic-directly#post-18161</link>
<pubDate>Fri, 07 Jan 2011 06:50:08 +0000</pubDate>
<dc:creator>renz</dc:creator>
<guid isPermaLink="false">18161@http://themeshaper.com/forums/</guid>
<description>&#60;p&#62;it is important to make a child theme???? cant we work on thematic directly
&#60;/p&#62;</description>
</item>

</channel>
</rss>
