<?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: WordPress is not YET an enterprise-level CMS</title>
	<atom:link href="http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/feed/" rel="self" type="application/rss+xml" />
	<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/</link>
	<description>We will turn your dreams into reality together!</description>
	<lastBuildDate>Thu, 27 Oct 2011 01:42:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Benjamin J. Balter</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-982</link>
		<dc:creator>Benjamin J. Balter</dc:creator>
		<pubDate>Mon, 29 Aug 2011 19:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-982</guid>
		<description>Great Question. Yes! Each site can have its own document repository (with the ability to give users different permissions on each repository), or you can create one shared document repository across all sites.

Think that would be an awesome post (there&#039;s not much out there like that -- at least not recently). Let me know if there&#039;s any way I can be helpful.

- Ben</description>
		<content:encoded><![CDATA[<p>Great Question. Yes! Each site can have its own document repository (with the ability to give users different permissions on each repository), or you can create one shared document repository across all sites.</p>
<p>Think that would be an awesome post (there&#8217;s not much out there like that &#8212; at least not recently). Let me know if there&#8217;s any way I can be helpful.</p>
<p>- Ben</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-981</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Mon, 29 Aug 2011 18:51:44 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-981</guid>
		<description>That looks like a fantastic plugin Ben!

Does it work well with a multi-site install? I could see a great case being made for the speed at which one could deploy a new project or team micro-site with DMS, blog and other functionality.

Perhaps when I re-visit this post I&#039;ll try to do a comparison between the cost, complexity and configurability between WordPress and other open source CMS&#039;s with &quot;enterprise-level&quot; alternatives like Interwoven Teamsite, Microsoft Sharepoint, OpenText RedDot, etc.</description>
		<content:encoded><![CDATA[<p>That looks like a fantastic plugin Ben!</p>
<p>Does it work well with a multi-site install? I could see a great case being made for the speed at which one could deploy a new project or team micro-site with DMS, blog and other functionality.</p>
<p>Perhaps when I re-visit this post I&#8217;ll try to do a comparison between the cost, complexity and configurability between WordPress and other open source CMS&#8217;s with &#8220;enterprise-level&#8221; alternatives like Interwoven Teamsite, Microsoft Sharepoint, OpenText RedDot, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benjamin J. Balter</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-980</link>
		<dc:creator>Benjamin J. Balter</dc:creator>
		<pubDate>Mon, 29 Aug 2011 16:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-980</guid>
		<description>Great write up! Really touched on all the key points of comparison.

Regarding &quot;workflow management&quot;  you may want to take a look at &lt;a href=&quot;http://ben.balter.com/2011/08/29/document-management-version-control-for-wordpress/&quot; rel=&quot;nofollow&quot;&gt;WP Document Revisions&lt;/a&gt; which is (1) A document management system (DMS), to track, store, and organize files of any format; (2) A collaboration tool to empower teams to collaboratively draft, edit, and refine documents; and (3) A file hosting solution to publish and securely deliver files to a team, to clients, or to the public.

Hopefully the plugin should provide a bit more parity between WordPress and traditional enterprise CMSs.</description>
		<content:encoded><![CDATA[<p>Great write up! Really touched on all the key points of comparison.</p>
<p>Regarding &#8220;workflow management&#8221;  you may want to take a look at <a href="http://ben.balter.com/2011/08/29/document-management-version-control-for-wordpress/" rel="nofollow">WP Document Revisions</a> which is (1) A document management system (DMS), to track, store, and organize files of any format; (2) A collaboration tool to empower teams to collaboratively draft, edit, and refine documents; and (3) A file hosting solution to publish and securely deliver files to a team, to clients, or to the public.</p>
<p>Hopefully the plugin should provide a bit more parity between WordPress and traditional enterprise CMSs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-921</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Fri, 05 Aug 2011 16:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-921</guid>
		<description>What I do depends greatly on the level of change(s) I&#039;m deploying between the environments. I am quite excited to see Mark Jaquith&#039;s presentation from Wordcamp SF this year - &lt;a href=&quot;http://markjaquith.wordpress.com/2011/07/17/speaking-at-wordcamp-sf-2011/&quot; rel=&quot;nofollow&quot;&gt;Scaling, Servers, and Deploys — Oh My!&lt;/a&gt; - as I expect it will offer much in the way of best-practice information.</description>
		<content:encoded><![CDATA[<p>What I do depends greatly on the level of change(s) I&#8217;m deploying between the environments. I am quite excited to see Mark Jaquith&#8217;s presentation from Wordcamp SF this year &#8211; <a href="http://markjaquith.wordpress.com/2011/07/17/speaking-at-wordcamp-sf-2011/" rel="nofollow">Scaling, Servers, and Deploys — Oh My!</a> &#8211; as I expect it will offer much in the way of best-practice information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-874</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Fri, 24 Jun 2011 15:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-874</guid>
		<description>Great post and would love to see this continuously updated -- what a great resource!  One question about your well made point re: managing changes between dev, staging and production environments... What might you recommend to address this?


Thanks,
Shawn</description>
		<content:encoded><![CDATA[<p>Great post and would love to see this continuously updated &#8212; what a great resource!  One question about your well made point re: managing changes between dev, staging and production environments&#8230; What might you recommend to address this?</p>
<p>Thanks,<br />
Shawn</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-687</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Mon, 31 Jan 2011 14:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-687</guid>
		<description>Thanks for the feedback. This was originally written before 3.0 had launched with many core capabilities that significantly changed the equation. I did some minor updates to reflect those areas. Perhaps when 3.1 is released I&#039;ll revisit it.

The one specific area where I think WP still has a short-coming is the ability to promote / manage changes between dev, staging and production environments due to the database of WP hosting code, config and content.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback. This was originally written before 3.0 had launched with many core capabilities that significantly changed the equation. I did some minor updates to reflect those areas. Perhaps when 3.1 is released I&#8217;ll revisit it.</p>
<p>The one specific area where I think WP still has a short-coming is the ability to promote / manage changes between dev, staging and production environments due to the database of WP hosting code, config and content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: popo</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-686</link>
		<dc:creator>popo</dc:creator>
		<pubDate>Sun, 30 Jan 2011 10:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-686</guid>
		<description>I think it should be noted, that every one of your criticisms is completely addressable via plugins and/or customization.

Now before you say:  &quot;But wait, if it requires customization -- then it&#039;s not ready&quot;  -- Consider that Drupal (which everyone regards as an Enterprise CMS) *always* requires massive amounts of customization.  In fact, Drupal typically requires more.

Wordpress 2.0 was a blogging engine that pretended to be a CMS.

Wordpress 3.0 is a whole different animal, and is far better than many packages claiming to be &quot;enterprise&quot; CMS&#039;s.  

Those who argue that Wordpress 3.0 isn&#039;t ready, are typically using an out-of-the-box install, and criticizing the handful of features that don&#039;t meet their needs.  Instead, they should note that Wordpress 3.0 is infinitely expandable, extremely stable and easily customizable -- and *WICKED FAST* when cached well -- making it indeed, and enterprise level CMS.

Now -- let&#039;s cut down the competition:  Drupal is a dog.  Period.  I&#039;ve built probably 3 dozen sites with Drupal and it never ceases to amaze me what a chore it is to work with.  

Yes. It&#039;s stable.  Yes. It&#039;s powerful.  But it&#039;s a dog all the same, imho.

Wordpress kicks serious ass.  But you have to learn how to make it kick ass.</description>
		<content:encoded><![CDATA[<p>I think it should be noted, that every one of your criticisms is completely addressable via plugins and/or customization.</p>
<p>Now before you say:  &#8220;But wait, if it requires customization &#8212; then it&#8217;s not ready&#8221;  &#8212; Consider that Drupal (which everyone regards as an Enterprise CMS) *always* requires massive amounts of customization.  In fact, Drupal typically requires more.</p>
<p>WordPress 2.0 was a blogging engine that pretended to be a CMS.</p>
<p>WordPress 3.0 is a whole different animal, and is far better than many packages claiming to be &#8220;enterprise&#8221; CMS&#8217;s.  </p>
<p>Those who argue that WordPress 3.0 isn&#8217;t ready, are typically using an out-of-the-box install, and criticizing the handful of features that don&#8217;t meet their needs.  Instead, they should note that WordPress 3.0 is infinitely expandable, extremely stable and easily customizable &#8212; and *WICKED FAST* when cached well &#8212; making it indeed, and enterprise level CMS.</p>
<p>Now &#8212; let&#8217;s cut down the competition:  Drupal is a dog.  Period.  I&#8217;ve built probably 3 dozen sites with Drupal and it never ceases to amaze me what a chore it is to work with.  </p>
<p>Yes. It&#8217;s stable.  Yes. It&#8217;s powerful.  But it&#8217;s a dog all the same, imho.</p>
<p>WordPress kicks serious ass.  But you have to learn how to make it kick ass.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryce Winter</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-669</link>
		<dc:creator>Bryce Winter</dc:creator>
		<pubDate>Wed, 01 Dec 2010 22:08:05 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-669</guid>
		<description>I&#039;d love to read an update on this entry, now that 3 is out...</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to read an update on this entry, now that 3 is out&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Idealien</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-288</link>
		<dc:creator>Idealien</dc:creator>
		<pubDate>Sun, 25 Apr 2010 04:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-288</guid>
		<description>Just finished listening to 1 of the 4 part podcast on Commercializing Wordpress from WPTavern &lt;a href=&quot;http://www.wptavern.com/category/wordpress-weekly&quot; rel=&quot;nofollow&quot;&gt;WPWeekly&lt;/a&gt; and come away very inspired. Amongst those plugins that immediately caught my ear were the &lt;a href=&quot;http://www.copress.org/wiki/Edit_Flow_Project&quot; rel=&quot;nofollow&quot;&gt;Edit Flow&lt;/a&gt; project (aka CoPress) for workflow management towards newsrooms.</description>
		<content:encoded><![CDATA[<p>Just finished listening to 1 of the 4 part podcast on Commercializing WordPress from WPTavern <a href="http://www.wptavern.com/category/wordpress-weekly" rel="nofollow">WPWeekly</a> and come away very inspired. Amongst those plugins that immediately caught my ear were the <a href="http://www.copress.org/wiki/Edit_Flow_Project" rel="nofollow">Edit Flow</a> project (aka CoPress) for workflow management towards newsrooms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://idealienstudios.com/blog/wordpress-not-yet-enterprise-level-cms/comment-page-1/#comment-282</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Mon, 19 Apr 2010 12:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://idealienstudios.com/?p=700#comment-282</guid>
		<description>Chris - You are right that very little of the features / functionality a large business would be interested in has to do with public-facing areas of the website. They &quot;could&quot; run their website with a text-editor and FTP client. But most believe that the back-end content development / approval process they &lt;del datetime=&quot;2010-04-19T11:50:51+00:00&quot;&gt;require&lt;/del&gt; want limits the tools they could consider to publish a site.

I agree that &quot;Enterprise-level&quot; is a mostly generic term to set the sales narrative for the scale a system could support. However, when the bulk of WordPress narratives written on the web could be paraphrased as &quot;WordPress is a blog platform&quot;, I still think it is important to highlight just how versatile it is that it can be easily customized to support so many different use cases.</description>
		<content:encoded><![CDATA[<p>Chris &#8211; You are right that very little of the features / functionality a large business would be interested in has to do with public-facing areas of the website. They &#8220;could&#8221; run their website with a text-editor and FTP client. But most believe that the back-end content development / approval process they <del datetime="2010-04-19T11:50:51+00:00">require</del> want limits the tools they could consider to publish a site.</p>
<p>I agree that &#8220;Enterprise-level&#8221; is a mostly generic term to set the sales narrative for the scale a system could support. However, when the bulk of WordPress narratives written on the web could be paraphrased as &#8220;WordPress is a blog platform&#8221;, I still think it is important to highlight just how versatile it is that it can be easily customized to support so many different use cases.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

