<?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: Choosing a Content Management System</title>
	<atom:link href="http://www.doingmedia.net/2006/11/choosing-a-content-management-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.doingmedia.net/2006/11/choosing-a-content-management-system/</link>
	<description></description>
	<lastBuildDate>Thu, 14 Oct 2010 21:10:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: deepb</title>
		<link>http://www.doingmedia.net/2006/11/choosing-a-content-management-system/comment-page-1/#comment-1540</link>
		<dc:creator>deepb</dc:creator>
		<pubDate>Mon, 27 Nov 2006 07:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.themediacommunicator.com/2006/11/choosing-a-content-management-system/#comment-1540</guid>
		<description>I&#039;ve never been a big fan of content management systems for several reasons:

 - as mentioned, they&#039;re often used to solve problems that have nothing to do with content management.

 - you tend to see a lot of extra CMS features enabled where there&#039;s no natural &quot;fit&quot; for them (e.g., just because your CMS makes it easy to add a chat room to every web page doesn&#039;t mean that every web page should have a chat room).

 - I see far too may recognizable content management systems.  A CMS should be invisible to the end user, not instantly identifiable (for whatever reason).

I guess those aren&#039;t really problems with the actual CMS... just with how people choose to use them.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never been a big fan of content management systems for several reasons:</p>
<p> &#8211; as mentioned, they&#8217;re often used to solve problems that have nothing to do with content management.</p>
<p> &#8211; you tend to see a lot of extra CMS features enabled where there&#8217;s no natural &#8220;fit&#8221; for them (e.g., just because your CMS makes it easy to add a chat room to every web page doesn&#8217;t mean that every web page should have a chat room).</p>
<p> &#8211; I see far too may recognizable content management systems.  A CMS should be invisible to the end user, not instantly identifiable (for whatever reason).</p>
<p>I guess those aren&#8217;t really problems with the actual CMS&#8230; just with how people choose to use them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

