<?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 for BricaBox Blog</title>
	<atom:link href="http://blog.bricabox.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bricabox.com</link>
	<description>Threads of Social Knitting</description>
	<pubDate>Sat, 05 Jul 2008 20:00:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>Comment on BricaBox: Ning for Content? by Nir</title>
		<link>http://blog.bricabox.com/thread/82#comment-9219</link>
		<dc:creator>Nir</dc:creator>
		<pubDate>Mon, 05 May 2008 23:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/?p=82#comment-9219</guid>
		<description>I always thought of BricaBox as a CMS with a blog-like UI. Blogs gained popularity over previous, more fully featured, CMS because they were very easy to use. BricaBox lets you use the blog UI simplicity with far more varied content.

(As elevator pitches go, though, this might a bit lengthy... To be used on buildings of at least 20 floors ;))</description>
		<content:encoded><![CDATA[<p>I always thought of BricaBox as a CMS with a blog-like UI. Blogs gained popularity over previous, more fully featured, CMS because they were very easy to use. BricaBox lets you use the blog UI simplicity with far more varied content.</p>
<p>(As elevator pitches go, though, this might a bit lengthy&#8230; To be used on buildings of at least 20 floors ;))</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox: Ning for Content? by JC</title>
		<link>http://blog.bricabox.com/thread/82#comment-8971</link>
		<dc:creator>JC</dc:creator>
		<pubDate>Sat, 26 Apr 2008 03:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/?p=82#comment-8971</guid>
		<description>“With BricaBox, you can create a Social Content Application in minutes, with a few clicks, drags, and drops.” - Mr. Westheimer

The word "app" doesn't seem to convey the full intention of the software but I don't have an alternative yet.  

Perhaps you could try a non-web metaphor? 

BricaBox lets you build a personal Grand Central Station for the web.</description>
		<content:encoded><![CDATA[<p>“With BricaBox, you can create a Social Content Application in minutes, with a few clicks, drags, and drops.” - Mr. Westheimer</p>
<p>The word &#8220;app&#8221; doesn&#8217;t seem to convey the full intention of the software but I don&#8217;t have an alternative yet.  </p>
<p>Perhaps you could try a non-web metaphor? </p>
<p>BricaBox lets you build a personal Grand Central Station for the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox: Ning for Content? by Clyde Smith</title>
		<link>http://blog.bricabox.com/thread/82#comment-8890</link>
		<dc:creator>Clyde Smith</dc:creator>
		<pubDate>Tue, 22 Apr 2008 01:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/?p=82#comment-8890</guid>
		<description>Ning for Content is the clear winner.</description>
		<content:encoded><![CDATA[<p>Ning for Content is the clear winner.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox: Ning for Content? by Andrew Weissman</title>
		<link>http://blog.bricabox.com/thread/82#comment-8879</link>
		<dc:creator>Andrew Weissman</dc:creator>
		<pubDate>Mon, 21 Apr 2008 20:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/?p=82#comment-8879</guid>
		<description>Nate:

Still think it needs to be tighter - partners, customers, investors -- for better or worse, need a really tight statement (ie, organize the works information) -- Ning for Content is good, but tell me as a user what that does for me, and also I dont like descriptions that utilize someone else's brand.

it's getting there -- good luck</description>
		<content:encoded><![CDATA[<p>Nate:</p>
<p>Still think it needs to be tighter - partners, customers, investors &#8212; for better or worse, need a really tight statement (ie, organize the works information) &#8212; Ning for Content is good, but tell me as a user what that does for me, and also I dont like descriptions that utilize someone else&#8217;s brand.</p>
<p>it&#8217;s getting there &#8212; good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox: Ning for Content? by Kristian Hansen</title>
		<link>http://blog.bricabox.com/thread/82#comment-8806</link>
		<dc:creator>Kristian Hansen</dc:creator>
		<pubDate>Fri, 18 Apr 2008 22:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/?p=82#comment-8806</guid>
		<description>Bricabox is a content hub. It bridges the gap between social graphing, content creation and individual expression. 

A database of content from blogs to videos and calendars. It plays to them all.</description>
		<content:encoded><![CDATA[<p>Bricabox is a content hub. It bridges the gap between social graphing, content creation and individual expression. </p>
<p>A database of content from blogs to videos and calendars. It plays to them all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox Manifesto: Part 1 by Nate Westheimer</title>
		<link>http://blog.bricabox.com/thread/70#comment-5494</link>
		<dc:creator>Nate Westheimer</dc:creator>
		<pubDate>Tue, 12 Feb 2008 23:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/thread/70#comment-5494</guid>
		<description>That's a great comment, Bud. One of the ways we'll approach this issue is by opening an API in the future. This will allow us to focus on popularly used and needed features, and leave the niche work to interested developers. While it seems we're trying to be all things to all people, we really do have something to offer pretty much ever level of user. I'll work on showing that in a graph of some sort.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great comment, Bud. One of the ways we&#8217;ll approach this issue is by opening an API in the future. This will allow us to focus on popularly used and needed features, and leave the niche work to interested developers. While it seems we&#8217;re trying to be all things to all people, we really do have something to offer pretty much ever level of user. I&#8217;ll work on showing that in a graph of some sort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BricaBox Manifesto: Part 1 by Bud Caddell</title>
		<link>http://blog.bricabox.com/thread/70#comment-5489</link>
		<dc:creator>Bud Caddell</dc:creator>
		<pubDate>Tue, 12 Feb 2008 22:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/thread/70#comment-5489</guid>
		<description>Nate, excellent post and I'm definitely excited to see the full bricabox platform.

Feature scope is definitely a tough call. Look at Basecamp -- Jason says they purposefully leave higher-end functionality out of the program and would gladly point people up the food chain. They believe they serve a very specific niche of users. Is Bricabox of that mind-set? If so, I'd like to see that top diagram with user groups or levels, in terms of difficulty and knowledge.</description>
		<content:encoded><![CDATA[<p>Nate, excellent post and I&#8217;m definitely excited to see the full bricabox platform.</p>
<p>Feature scope is definitely a tough call. Look at Basecamp &#8212; Jason says they purposefully leave higher-end functionality out of the program and would gladly point people up the food chain. They believe they serve a very specific niche of users. Is Bricabox of that mind-set? If so, I&#8217;d like to see that top diagram with user groups or levels, in terms of difficulty and knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 1 Week to Launch and Kicking Ass by Tobn</title>
		<link>http://blog.bricabox.com/thread/46#comment-368</link>
		<dc:creator>Tobn</dc:creator>
		<pubDate>Fri, 02 Nov 2007 16:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bricabox.com/thread/46#comment-368</guid>
		<description>Congrats!  I'm looking forward to seeing this launch next week.  I got to see it a bit at Startup Camp, but didn't get to talk to you about it in too much depth.

Exciting time!</description>
		<content:encoded><![CDATA[<p>Congrats!  I&#8217;m looking forward to seeing this launch next week.  I got to see it a bit at Startup Camp, but didn&#8217;t get to talk to you about it in too much depth.</p>
<p>Exciting time!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
