<?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: What intranet CMS&#8217;s can learn from wikis</title>
	<atom:link href="http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/</link>
	<description>News and opinion on all things intranet &#38; CM</description>
	<lastBuildDate>Tue, 07 Feb 2012 04:15:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Segnalazioni nutrienti &#124; Intranet Management</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-1614</link>
		<dc:creator>Segnalazioni nutrienti &#124; Intranet Management</dc:creator>
		<pubDate>Wed, 27 Jan 2010 08:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-1614</guid>
		<description>[...] Che cosa i CMS possono imparare dai wiki. Un post di Column two. [...]</description>
		<content:encoded><![CDATA[<p>[...] Che cosa i CMS possono imparare dai wiki. Un post di Column two. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ThoughtFarmer Blog &#187; What can intranet CMSs learn from wikis? A lot.</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-1185</link>
		<dc:creator>ThoughtFarmer Blog &#187; What can intranet CMSs learn from wikis? A lot.</dc:creator>
		<pubDate>Tue, 26 May 2009 17:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-1185</guid>
		<description>[...] this background, I enjoyed reading James Robertson&#8217;s article today, &#8220;What Intranet CMS&#8217;s Can Learn From Wikis.&#8221; James always comes up with thoughtful, original material about intranets. In this article, [...]</description>
		<content:encoded><![CDATA[<p>[...] this background, I enjoyed reading James Robertson&#8217;s article today, &#8220;What Intranet CMS&#8217;s Can Learn From Wikis.&#8221; James always comes up with thoughtful, original material about intranets. In this article, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What can intranet CMSs learn from wikis? A lot. &#171; ThoughtFarmer</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-1148</link>
		<dc:creator>What can intranet CMSs learn from wikis? A lot. &#171; ThoughtFarmer</dc:creator>
		<pubDate>Tue, 21 Apr 2009 22:13:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-1148</guid>
		<description>[...] this background, I enjoyed reading James Robertson&#8217;s article today, &#8220;What Intranet CMS&#8217;s Can Learn From Wikis.&#8221; James always comes up with thoughtful, original material about intranets. In this article, [...]</description>
		<content:encoded><![CDATA[<p>[...] this background, I enjoyed reading James Robertson&#8217;s article today, &#8220;What Intranet CMS&#8217;s Can Learn From Wikis.&#8221; James always comes up with thoughtful, original material about intranets. In this article, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DokuBlog &#187; Blog Archive &#187; What&#8217;s The Difference Between a Wiki and a CMS?</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-188</link>
		<dc:creator>DokuBlog &#187; Blog Archive &#187; What&#8217;s The Difference Between a Wiki and a CMS?</dc:creator>
		<pubDate>Wed, 01 Oct 2008 10:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-188</guid>
		<description>[...] it was refreshing to see James Robertson’s article What intranet CMS’s can learn from wikis:  At the end of the day, I don’t care about the publishing tools that underpin the intranet, as [...]</description>
		<content:encoded><![CDATA[<p>[...] it was refreshing to see James Robertson’s article What intranet CMS’s can learn from wikis:  At the end of the day, I don’t care about the publishing tools that underpin the intranet, as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niels Hartvig</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-187</link>
		<dc:creator>Niels Hartvig</dc:creator>
		<pubDate>Wed, 01 Oct 2008 08:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-187</guid>
		<description>Great points!

When we created the latest revision of umbraco (an open source ASP.NET Web CMS), we were very inspired by the wiki editing process, especially the idea of editing in context rather than in a back office tool. 

So we found a great user-friendly way (at least we like to think so ;-)) to combine the ease of existing editor controls - which means that you don&#039;t need to learn a new syntax - with the in-context wiki paradigm and still and ended up with something called LiveEditing. 

The feature is shown in this podcast featuring a very enthusiastic dev team:
http://umbraco.org/blog/2008/8/30/podcast-7---the-live-editing-progress

Thoughts?

btw: I think a lot of us will be missing points like these at jboye08 :&#039;-(</description>
		<content:encoded><![CDATA[<p>Great points!</p>
<p>When we created the latest revision of umbraco (an open source ASP.NET Web CMS), we were very inspired by the wiki editing process, especially the idea of editing in context rather than in a back office tool. </p>
<p>So we found a great user-friendly way (at least we like to think so <img src='http://www.steptwo.com.au/columntwo/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> ) to combine the ease of existing editor controls &#8211; which means that you don&#8217;t need to learn a new syntax &#8211; with the in-context wiki paradigm and still and ended up with something called LiveEditing. </p>
<p>The feature is shown in this podcast featuring a very enthusiastic dev team:<br />
<a href="http://umbraco.org/blog/2008/8/30/podcast-7---the-live-editing-progress" rel="nofollow">http://umbraco.org/blog/2008/8/30/podcast-7&#8212;the-live-editing-progress</a></p>
<p>Thoughts?</p>
<p>btw: I think a lot of us will be missing points like these at jboye08 :&#8217;-(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-176</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Mon, 29 Sep 2008 20:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-176</guid>
		<description>The key thing for me is this: not all content needs to be of equal content. Both intranets and wikis need to recognise this.

There is core/important content that *must* be right, and of high quality. This should be published by trained authors, and maybe even reviewed.

As you get further away from the &quot;centre&quot;, the need for quality drops. At the outer edge, there&#039;s content that we really don&#039;t care about at all, because usage is too local, or it&#039;s not accessed frequently enough.

So there&#039;s space (and a need) for all authoring models, from tight control to loose publishing.</description>
		<content:encoded><![CDATA[<p>The key thing for me is this: not all content needs to be of equal content. Both intranets and wikis need to recognise this.</p>
<p>There is core/important content that *must* be right, and of high quality. This should be published by trained authors, and maybe even reviewed.</p>
<p>As you get further away from the &#8220;centre&#8221;, the need for quality drops. At the outer edge, there&#8217;s content that we really don&#8217;t care about at all, because usage is too local, or it&#8217;s not accessed frequently enough.</p>
<p>So there&#8217;s space (and a need) for all authoring models, from tight control to loose publishing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Symphonious &#187; What&#8217;s The Difference Between a Wiki and a CMS?</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-175</link>
		<dc:creator>Symphonious &#187; What&#8217;s The Difference Between a Wiki and a CMS?</dc:creator>
		<pubDate>Mon, 29 Sep 2008 14:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-175</guid>
		<description>[...] So it was refreshing to see James Robertson’s article What intranet CMS’s can learn from wikis: [...]</description>
		<content:encoded><![CDATA[<p>[...] So it was refreshing to see James Robertson’s article What intranet CMS’s can learn from wikis: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim van Waard</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-173</link>
		<dc:creator>Tim van Waard</dc:creator>
		<pubDate>Mon, 29 Sep 2008 08:47:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-173</guid>
		<description>Certainly, lowering or giving up control will lead to more participation. On the other hand, I think it&#039;s necessary to train participants on an intranet extensively. 

We are currently giving courses to people how to use intranet, and then give them selfcontrol on the &quot;staging&quot; environment (which is sort of a test environment).

They give us a sign, we check if it looks nice and then publish to live, which is the environment where everyone can see it.

But educating the people about the intranet is necessary, otherwise it will be a mess in no time unfortunately.</description>
		<content:encoded><![CDATA[<p>Certainly, lowering or giving up control will lead to more participation. On the other hand, I think it&#8217;s necessary to train participants on an intranet extensively. </p>
<p>We are currently giving courses to people how to use intranet, and then give them selfcontrol on the &#8220;staging&#8221; environment (which is sort of a test environment).</p>
<p>They give us a sign, we check if it looks nice and then publish to live, which is the environment where everyone can see it.</p>
<p>But educating the people about the intranet is necessary, otherwise it will be a mess in no time unfortunately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stuart Murnain</title>
		<link>http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/comment-page-1/#comment-167</link>
		<dc:creator>Stuart Murnain</dc:creator>
		<pubDate>Sun, 28 Sep 2008 23:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/columntwo/?p=2907#comment-167</guid>
		<description>I agree with your points. In the trenches, the most difficult thing is convincing management to give up control - that a wiki-like intranet does not lead to:
* general chaos and time-wasting
* diluting of &quot;official&quot; content with commentary and &quot;non-official&quot; points of view

In my experience, the bits of the intranet that we did free up for general authorship became much better used and rarely required moderator intervention.</description>
		<content:encoded><![CDATA[<p>I agree with your points. In the trenches, the most difficult thing is convincing management to give up control &#8211; that a wiki-like intranet does not lead to:<br />
* general chaos and time-wasting<br />
* diluting of &#8220;official&#8221; content with commentary and &#8220;non-official&#8221; points of view</p>
<p>In my experience, the bits of the intranet that we did free up for general authorship became much better used and rarely required moderator intervention.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

