<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Carrington JAM (Just Add Markup) 1.1</title>
	<atom:link href="http://carringtontheme.com/2009/03/carrington-jam-just-add-markup-11/feed/" rel="self" type="application/rss+xml" />
	<link>http://carringtontheme.com/2009/03/carrington-jam-just-add-markup-11/</link>
	<description>The CMS Theme Framework for WordPress</description>
	<lastBuildDate>Thu, 11 Mar 2010 06:56:15 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alex King</title>
		<link>http://carringtontheme.com/2009/03/carrington-jam-just-add-markup-11/comment-page-1/#comment-1903</link>
		<dc:creator>Alex King</dc:creator>
		<pubDate>Thu, 28 May 2009 21:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://carringtontheme.com/?p=100#comment-1903</guid>
		<description>&lt;blockquote&gt;I’m actually meant to take these template files and edit them directly, right?&lt;/blockquote&gt;

Yes, Carrington is a real theme framework (think developer frameworks like Rails for Ruby and Jango for Python, etc.) - not a parent theme. Carrington JAM is a bare-bones skeleton theme that uses the framework.

&lt;blockquote&gt;Suppose I take Carrington Jam 1.1 and build a custom theme with it: if you put out a new version like 1.2, I’m not really meant to upgrade my custom theme, am I?&lt;/blockquote&gt;

Correct - there is nothing in JAM that has any upgrade value.

&lt;blockquote&gt;If a new version of Carrington Core comes out, though, I could upgrade the files for the core in my theme, right?&lt;/blockquote&gt;

Correct again, and you get the new framework enhancements.</description>
		<content:encoded><![CDATA[<blockquote><p>I’m actually meant to take these template files and edit them directly, right?</p></blockquote>
<p>Yes, Carrington is a real theme framework (think developer frameworks like Rails for Ruby and Jango for Python, etc.) &#8211; not a parent theme. Carrington JAM is a bare-bones skeleton theme that uses the framework.</p>
<blockquote><p>Suppose I take Carrington Jam 1.1 and build a custom theme with it: if you put out a new version like 1.2, I’m not really meant to upgrade my custom theme, am I?</p></blockquote>
<p>Correct &#8211; there is nothing in JAM that has any upgrade value.</p>
<blockquote><p>If a new version of Carrington Core comes out, though, I could upgrade the files for the core in my theme, right?</p></blockquote>
<p>Correct again, and you get the new framework enhancements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy</title>
		<link>http://carringtontheme.com/2009/03/carrington-jam-just-add-markup-11/comment-page-1/#comment-1901</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Thu, 28 May 2009 21:44:32 +0000</pubDate>
		<guid isPermaLink="false">http://carringtontheme.com/?p=100#comment-1901</guid>
		<description>I hate to sound dense, but Carrington Jam is not really meant to be something like a parent theme, is it? I&#039;m not meant to create a child theme that draws on this, am I? I&#039;m actually meant to take these template files and edit them directly, right? I just want to make sure that I&#039;m not missing something obvious.

Two other questions:

* Suppose I take Carrington Jam 1.1 and build a custom theme with it: if you put out a new version like 1.2, I&#039;m not really meant to upgrade my custom theme, am I?
* If a new version of Carrington Core comes out, though, I could upgrade the files for the core in my theme, right?

Thanks,
~randy</description>
		<content:encoded><![CDATA[<p>I hate to sound dense, but Carrington Jam is not really meant to be something like a parent theme, is it? I&#8217;m not meant to create a child theme that draws on this, am I? I&#8217;m actually meant to take these template files and edit them directly, right? I just want to make sure that I&#8217;m not missing something obvious.</p>
<p>Two other questions:</p>
<p>* Suppose I take Carrington Jam 1.1 and build a custom theme with it: if you put out a new version like 1.2, I&#8217;m not really meant to upgrade my custom theme, am I?<br />
* If a new version of Carrington Core comes out, though, I could upgrade the files for the core in my theme, right?</p>
<p>Thanks,<br />
~randy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
