<?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: The nasty four-letter word that must be banished from the web</title>
	<atom:link href="http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/</link>
	<description></description>
	<lastBuildDate>Sun, 14 Mar 2010 15:23:10 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Westra</title>
		<link>http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/comment-page-1/#comment-118843</link>
		<dc:creator>John Westra</dc:creator>
		<pubDate>Fri, 29 Feb 2008 18:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/#comment-118843</guid>
		<description>New Google Sites Application Misses Mark

After waiting expectantly for the release of Google Sites, the success to Jotspot, for more than a year, I must confess I&#039;m pretty disappointed in the result. The user interface is clunky and non-intuitive and offers little new in the way of collaborative tools, other than Joomla-esq shared web page editing.

What happened? Google already has a terrific widget enabled web page creation tool. It&#039;s called Blogger! Why didn&#039;t they use that technology to make dropping various functional elements onto a page easy?

The ability to quickly create an Intranet/Xtranet of four to twenty pages is what most of my SMB clients are looking for. Doing this with SharePoint has always been too developer and infrastructure intensive, leaving us to recommend products like WebOffice (formerly Intranets.com) and Blue Tie as web-based collaboration tools.

BlueTie in unique in that it offers unique ways for partners to monetize the solution and generate a unique ongoing revenue stream. In fact, BlueTie was recently recognized as an OnMedia Top 100 Winner.

Google has missed the mark badly with its Google Sites application. It&#039;s unfortunate, because it takes the pressure off Microsoft to improve SharePoint&#039;s ease of use and Cisco to lower the cost of WebOffice.

Until Google releases a Google Sites application that is significantly easier to use and functional, I will continue to recommend WebOffice, Blue Tie or our own TeamPro application as a Intranet/Xtranet solution.</description>
		<content:encoded><![CDATA[<p>New Google Sites Application Misses Mark</p>
<p>After waiting expectantly for the release of Google Sites, the success to Jotspot, for more than a year, I must confess I&#8217;m pretty disappointed in the result. The user interface is clunky and non-intuitive and offers little new in the way of collaborative tools, other than Joomla-esq shared web page editing.</p>
<p>What happened? Google already has a terrific widget enabled web page creation tool. It&#8217;s called Blogger! Why didn&#8217;t they use that technology to make dropping various functional elements onto a page easy?</p>
<p>The ability to quickly create an Intranet/Xtranet of four to twenty pages is what most of my SMB clients are looking for. Doing this with SharePoint has always been too developer and infrastructure intensive, leaving us to recommend products like WebOffice (formerly Intranets.com) and Blue Tie as web-based collaboration tools.</p>
<p>BlueTie in unique in that it offers unique ways for partners to monetize the solution and generate a unique ongoing revenue stream. In fact, BlueTie was recently recognized as an OnMedia Top 100 Winner.</p>
<p>Google has missed the mark badly with its Google Sites application. It&#8217;s unfortunate, because it takes the pressure off Microsoft to improve SharePoint&#8217;s ease of use and Cisco to lower the cost of WebOffice.</p>
<p>Until Google releases a Google Sites application that is significantly easier to use and functional, I will continue to recommend WebOffice, Blue Tie or our own TeamPro application as a Intranet/Xtranet solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guy</title>
		<link>http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/comment-page-1/#comment-118664</link>
		<dc:creator>Guy</dc:creator>
		<pubDate>Thu, 28 Feb 2008 14:50:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/#comment-118664</guid>
		<description>From what I see of their marketing materials so far, they are promoting Google Sites as a replacement for online website authoring tools. The various examples they give are all basically the same thing - pages with various, presumably templated, containers. I&#039;ve not been able to get in and test because it will likely munge my other google services associated with my email address (quite annoying) but I can see where they are coming from - they see the underlying wiki technology as a great way to make common website scenarios easily editable online.</description>
		<content:encoded><![CDATA[<p>From what I see of their marketing materials so far, they are promoting Google Sites as a replacement for online website authoring tools. The various examples they give are all basically the same thing &#8211; pages with various, presumably templated, containers. I&#8217;ve not been able to get in and test because it will likely munge my other google services associated with my email address (quite annoying) but I can see where they are coming from &#8211; they see the underlying wiki technology as a great way to make common website scenarios easily editable online.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xavier</title>
		<link>http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/comment-page-1/#comment-118621</link>
		<dc:creator>Xavier</dc:creator>
		<pubDate>Thu, 28 Feb 2008 10:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ikiw.org/2008/02/28/the-nasty-four-letter-word-that-must-be-banished-from-the-web/#comment-118621</guid>
		<description>I&#039;m not sure I fully agree with you.

The term &#039;wiki&#039; scares a whole lot of people who are not really into this whole web 2.0 / Enterprise 2.0 stuff ...

Also that term generally brings the word &#039;wikipedia&#039; in their mind, and the use of the wiki technology can bring something completely different,which confuses those people even more ...

I&#039;m starting to lobby inside our organization to implement blogs and collaborative online spaces (yes, wikis! ;o)),and I can tell you that its easier to tell people about a document that different people can contribute to, rather than using the word wiki ...</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I fully agree with you.</p>
<p>The term &#8216;wiki&#8217; scares a whole lot of people who are not really into this whole web 2.0 / Enterprise 2.0 stuff &#8230;</p>
<p>Also that term generally brings the word &#8216;wikipedia&#8217; in their mind, and the use of the wiki technology can bring something completely different,which confuses those people even more &#8230;</p>
<p>I&#8217;m starting to lobby inside our organization to implement blogs and collaborative online spaces (yes, wikis! ;o)),and I can tell you that its easier to tell people about a document that different people can contribute to, rather than using the word wiki &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
