<?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: Why should I go for a CMS based website?</title>
	<atom:link href="http://webmasterfocus.net/why-should-i-go-for-a-cms-based-website/feed" rel="self" type="application/rss+xml" />
	<link>http://webmasterfocus.net/why-should-i-go-for-a-cms-based-website</link>
	<description></description>
	<pubDate>Sat, 13 Mar 2010 10:45:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark, Ars Logo Design</title>
		<link>http://webmasterfocus.net/why-should-i-go-for-a-cms-based-website/comment-page-1#comment-487</link>
		<dc:creator>Mark, Ars Logo Design</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://webmasterfocus.net/?p=264#comment-487</guid>
		<description>CMS engines offer advantages to content-intensive websites because they make the whole publication process easier. They allow non-technical user to publish information in a few steps, without needing to have html coding skills. They usually have a WYSIWYG interface to control the appearence of content on page. On the other hand, CMS engines restrict the layout of content on page, as templates are used to publish the content.</description>
		<content:encoded><![CDATA[<p>CMS engines offer advantages to content-intensive websites because they make the whole publication process easier. They allow non-technical user to publish information in a few steps, without needing to have html coding skills. They usually have a WYSIWYG interface to control the appearence of content on page. On the other hand, CMS engines restrict the layout of content on page, as templates are used to publish the content.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
