<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Support team knowledge : blog and wiki?</title>
	<link>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/</link>
	<description>sharing ideas thoughts and feedback</description>
	<pubDate>Sat, 28 Nov 2009 15:54:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Johan Jenefeldt</title>
		<link>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32653</link>
		<pubDate>Wed, 29 Oct 2008 18:56:39 +0000</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32653</guid>
					<description>About subscribing to the wiki - Some wikis support subscribing only if major changes has been made to the page. So if a spelling correction is made, you wont be bothered. Stewart should know about this, he's the pro after all.</description>
		<content:encoded><![CDATA[	<p>About subscribing to the wiki - Some wikis support subscribing only if major changes has been made to the page. So if a spelling correction is made, you wont be bothered. Stewart should know about this, he&#8217;s the pro after all.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Johnt</title>
		<link>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32475</link>
		<pubDate>Tue, 06 May 2008 08:05:13 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32475</guid>
					<description>Thanks for your input Stewart.

My plan is to use a blog for tips and experiences, and use the wiki for solutions.

If it's a solution of importance, there's no reason why we can't publish a blog post pointing to the solution in the wiki.

In the blog post we would have to state, &quot;if you have comments, please leave them on the wikipage and not in this blog posts&quot;</description>
		<content:encoded><![CDATA[	<p>Thanks for your input Stewart.</p>
	<p>My plan is to use a blog for tips and experiences, and use the wiki for solutions.</p>
	<p>If it&#8217;s a solution of importance, there&#8217;s no reason why we can&#8217;t publish a blog post pointing to the solution in the wiki.</p>
	<p>In the blog post we would have to state, &#8220;if you have comments, please leave them on the wikipage and not in this blog posts&#8221;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stewart Mader</title>
		<link>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32474</link>
		<pubDate>Tue, 06 May 2008 05:32:08 +0100</pubDate>
		<guid>http://libraryclips.blogsome.com/2008/04/17/support-team-knowledge-blog-and-wiki/#comment-32474</guid>
					<description>John,
This is excellent! One of the best wiki uses in support is to build a central knowledge base so that people aren't keeping the knowledge to themselves - which isn't their fault, really. Until the wiki comes along, they have no good place to post the questions they commonly get asked, and the answers they've developed. 

Once the wiki is in place, they can add these questions, and list their answers. Then, others can add to those answers, refine them, and make them more comprehensive as they encounter different scenarios, etc.

A blog can work hand in hand with the wiki as a means to call out content on the wiki and direct people to it. For example, if one person gets asked a particularly complex new question, they can post their answer on the wiki, then publish a quick blog post letting others know about the new question and asking if anyone else has answers to share. This is a great way to jumpstart contributions to a particular wiki page.
Regards,
Stewart</description>
		<content:encoded><![CDATA[	<p>John,<br />
This is excellent! One of the best wiki uses in support is to build a central knowledge base so that people aren&#8217;t keeping the knowledge to themselves - which isn&#8217;t their fault, really. Until the wiki comes along, they have no good place to post the questions they commonly get asked, and the answers they&#8217;ve developed. </p>
	<p>Once the wiki is in place, they can add these questions, and list their answers. Then, others can add to those answers, refine them, and make them more comprehensive as they encounter different scenarios, etc.</p>
	<p>A blog can work hand in hand with the wiki as a means to call out content on the wiki and direct people to it. For example, if one person gets asked a particularly complex new question, they can post their answer on the wiki, then publish a quick blog post letting others know about the new question and asking if anyone else has answers to share. This is a great way to jumpstart contributions to a particular wiki page.<br />
Regards,<br />
Stewart
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
