<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Internet facing MOSS sites without content deployment</title><link>http://blogs.msdn.com/vesku/archive/2009/01/29/internet-facing-moss-sites-without-content-deployment.aspx</link><description>Lately there has been quite a lot of discussions concerning Internet facing MOSS sites and content deployment . Quite often there’s misconception that MOSS cannot be used as Internet facing platform without separate authoring farm and utilizing content</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>
		   Internet facing MOSS sites without content deployment &amp;raquo; Click &amp;amp; Solve	</title><link>http://blogs.msdn.com/vesku/archive/2009/01/29/internet-facing-moss-sites-without-content-deployment.aspx#9383726</link><pubDate>Fri, 30 Jan 2009 00:52:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9383726</guid><dc:creator>
		   Internet facing MOSS sites without content deployment &amp;raquo; Click &amp;amp; Solve	</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.clickandsolve.com/?p=1967"&gt;http://www.clickandsolve.com/?p=1967&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: Internet facing MOSS sites without content deployment</title><link>http://blogs.msdn.com/vesku/archive/2009/01/29/internet-facing-moss-sites-without-content-deployment.aspx#9847752</link><pubDate>Fri, 24 Jul 2009 21:02:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9847752</guid><dc:creator>rdub</dc:creator><description>&lt;p&gt;Content Deployment adds way too much risk and issues for any benefit it actually offers. &amp;nbsp;If you are thinking about using content deployment to move content (on a regular basis) from a single authoring environment to a single production environment then I highly recommend just editing directly in the production environment.&lt;/p&gt;
</description></item></channel></rss>