<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Wordpress as CMS - Section Management</title>
	<link>http://www.archetyped.com/blog/wordpress-as-cms-section-management/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 22:30:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Wordpress as CMS - Extensions, Who Needs &#8216;em? at Archetyped</title>
		<link>http://www.archetyped.com/blog/wordpress-as-cms-section-management/#comment-12</link>
		<pubDate>Sat, 26 Aug 2006 09:27:46 +0000</pubDate>
		<guid>http://www.archetyped.com/blog/wordpress-as-cms-section-management/#comment-12</guid>
					<description>[...] I&#8217;ll admit, when I first added the option for a user-definable extension to posts (i.e. post-name.html), I did it because it was the only way to get the darn thing working. I needed that extra bit of text to help differentiate sections from posts from categories from tags. Without it, Wordpress couldn&#8217;t determine how to handle the different requests. Well, since then (a whole 3 days ago), I&#8217;ve become more familiar with the zen of rewrite rules (though they still mostly remain shrouded in mystery), and along with some refinement in the way sections are managed, I&#8217;ve been able to do away with the requirement for faux file extensions entirely. Note that I did not do away with the extensions themselves. If you want them, you can add whatever extension you like. But they are no longer required, and that&#8217;s the important bit. I don&#8217;t know if I just got used to having them around these past few days, but I actually think I like having an extension appended to the post&#8217;s title better that not having one. There&#8217;s a few reasons for this: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I&#8217;ll admit, when I first added the option for a user-definable extension to posts (i.e. post-name.html), I did it because it was the only way to get the darn thing working. I needed that extra bit of text to help differentiate sections from posts from categories from tags. Without it, Wordpress couldn&#8217;t determine how to handle the different requests. Well, since then (a whole 3 days ago), I&#8217;ve become more familiar with the zen of rewrite rules (though they still mostly remain shrouded in mystery), and along with some refinement in the way sections are managed, I&#8217;ve been able to do away with the requirement for faux file extensions entirely. Note that I did not do away with the extensions themselves. If you want them, you can add whatever extension you like. But they are no longer required, and that&#8217;s the important bit. I don&#8217;t know if I just got used to having them around these past few days, but I actually think I like having an extension appended to the post&#8217;s title better that not having one. There&#8217;s a few reasons for this: [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: CMS Planet &#187; Wordpress as CMS - Section Management</title>
		<link>http://www.archetyped.com/blog/wordpress-as-cms-section-management/#comment-8</link>
		<pubDate>Tue, 22 Aug 2006 13:44:11 +0000</pubDate>
		<guid>http://www.archetyped.com/blog/wordpress-as-cms-section-management/#comment-8</guid>
					<description>[...] Original post by Archetyped. To read the full article visit: Archetyped [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Original post by Archetyped. To read the full article visit: Archetyped [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
