<?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"
	>
<channel>
	<title>Comments on: CMS Review: Bricolage</title>
	<atom:link href="http://www.nautis.com/2007/08/17/cms-review-bricolage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nautis.com/2007/08/17/cms-review-bricolage/</link>
	<description>Jung, Sheldrake, Campbell, Bergson &#038; Me</description>
	<pubDate>Fri, 16 May 2008 08:04:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Matthew</title>
		<link>http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10273</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Fri, 24 Aug 2007 23:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10273</guid>
		<description>Thanks for the feedback. I'm glad it has generated some discussion. I'm also happy to have any errors corrected, so thank you.

I think the intent of the review is somehow being overlooked though. I'm not very technical and usually work as a consultant representing the business in vendor selections. An IT Director or CIO looks for very different things than a developer might. I'm no expert but I have been at this for a &lt;a href="http://www.cmswatch.com/Feature/109-Project-Collaboration" rel="nofollow"&gt;little&lt;/a&gt; &lt;a href="http://www.cmswatch.com/Feature/97" rel="nofollow"&gt;while&lt;/a&gt;. Obviously, these are just my views. However, you may find that a business analyst doing broad research on open source content management systems would come to conclusions very similar to mine. My job is to make recommendations and often this doesn't allow for several weeks of in depth study of each product. These decisions are based mostly on the criteria I've listed above (the same criteria used in the &lt;a href="http://www.cmswatch.com/" rel="nofollow"&gt;CMS Watch Report&lt;/a&gt;). I had many great things to say about the product. That seems to have been missed. I hope that over time the project does grow and thrive.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback. I&#8217;m glad it has generated some discussion. I&#8217;m also happy to have any errors corrected, so thank you.</p>
<p>I think the intent of the review is somehow being overlooked though. I&#8217;m not very technical and usually work as a consultant representing the business in vendor selections. An IT Director or CIO looks for very different things than a developer might. I&#8217;m no expert but I have been at this for a <a href="http://www.cmswatch.com/Feature/109-Project-Collaboration" rel="nofollow">little</a> <a href="http://www.cmswatch.com/Feature/97" rel="nofollow">while</a>. Obviously, these are just my views. However, you may find that a business analyst doing broad research on open source content management systems would come to conclusions very similar to mine. My job is to make recommendations and often this doesn&#8217;t allow for several weeks of in depth study of each product. These decisions are based mostly on the criteria I&#8217;ve listed above (the same criteria used in the <a href="http://www.cmswatch.com/" rel="nofollow">CMS Watch Report</a>). I had many great things to say about the product. That seems to have been missed. I hope that over time the project does grow and thrive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phillip Smith</title>
		<link>http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10272</link>
		<dc:creator>Phillip Smith</dc:creator>
		<pubDate>Fri, 24 Aug 2007 15:22:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10272</guid>
		<description>The Bricolage community certainly doesn't seem "dead" to me: http://marc.info/?l=bricolage-general&#38;m=118779275913145&#38;w=2</description>
		<content:encoded><![CDATA[<p>The Bricolage community certainly doesn&#8217;t seem &#8220;dead&#8221; to me: <a href="http://marc.info/?l=bricolage-general&amp;m=118779275913145&amp;w=2" rel="nofollow">http://marc.info/?l=bricolage-general&amp;m=118779275913145&amp;w=2</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cameron</title>
		<link>http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10271</link>
		<dc:creator>cameron</dc:creator>
		<pubDate>Wed, 22 Aug 2007 14:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10271</guid>
		<description>Some inaccuracies in this article:

"Delivery options that WCMS owners have come to take for granted such as blogs, wikis, and FAQ tools are missing from Bricolage."

Bricolage is not a content display engine.  It is completely removed from display of the final content.  One can publish any blog, wiki, even another instance of bricolage through bricolage.

"The lack of an inline editing feature is also a serious drawback."

A couple of WYSIWIG editing packages are supported.  If you mean on the live page inline editing, you have just lost workflow control...

"Bricolage is built specifically for Linux"

I believe a lot of the initial development took place on Apple OSX, but I think Linux is the most popular platform.

"For all of its strengths, perl seems to be going the way of the dinosaur."

Supporting reference?

"Bricolage has no virtualization module to view a site in its pre-production state."

Preview publishing is built in and works fine.</description>
		<content:encoded><![CDATA[<p>Some inaccuracies in this article:</p>
<p>&#8220;Delivery options that WCMS owners have come to take for granted such as blogs, wikis, and FAQ tools are missing from Bricolage.&#8221;</p>
<p>Bricolage is not a content display engine.  It is completely removed from display of the final content.  One can publish any blog, wiki, even another instance of bricolage through bricolage.</p>
<p>&#8220;The lack of an inline editing feature is also a serious drawback.&#8221;</p>
<p>A couple of WYSIWIG editing packages are supported.  If you mean on the live page inline editing, you have just lost workflow control&#8230;</p>
<p>&#8220;Bricolage is built specifically for Linux&#8221;</p>
<p>I believe a lot of the initial development took place on Apple OSX, but I think Linux is the most popular platform.</p>
<p>&#8220;For all of its strengths, perl seems to be going the way of the dinosaur.&#8221;</p>
<p>Supporting reference?</p>
<p>&#8220;Bricolage has no virtualization module to view a site in its pre-production state.&#8221;</p>
<p>Preview publishing is built in and works fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Orrock</title>
		<link>http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10270</link>
		<dc:creator>Paul Orrock</dc:creator>
		<pubDate>Wed, 22 Aug 2007 14:36:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.nautis.com/2007/08/17/cms-review-bricolage/#comment-10270</guid>
		<description>Hi,

Just a note to say Bricolage isn't dead, we have a very active user and development mailing lists, with the core development team still active and adding features.

In fact the latest version of Bricolage was released a week before this article was published.

While it's true that David is no longer actively involved in development of Bricolage, he is still active on the mailing lists.

Commercial support is now offered by several companies and we're committed to keeping Bricolage going for all the reasons you mention.

regards,

Paul</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Just a note to say Bricolage isn&#8217;t dead, we have a very active user and development mailing lists, with the core development team still active and adding features.</p>
<p>In fact the latest version of Bricolage was released a week before this article was published.</p>
<p>While it&#8217;s true that David is no longer actively involved in development of Bricolage, he is still active on the mailing lists.</p>
<p>Commercial support is now offered by several companies and we&#8217;re committed to keeping Bricolage going for all the reasons you mention.</p>
<p>regards,</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
