<?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: In-context vs back-end authoring</title>
	<atom:link href="http://www.steptwo.com.au/papers/cmb_incontext/index.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.steptwo.com.au/papers/cmb_incontext/index.html</link>
	<description>Beyond The Idea</description>
	<lastBuildDate>Tue, 16 Mar 2010 17:29:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wilf</title>
		<link>http://www.steptwo.com.au/papers/cmb_incontext/index.html/comment-page-1#comment-1270</link>
		<dc:creator>Wilf</dc:creator>
		<pubDate>Wed, 06 Jan 2010 04:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=106#comment-1270</guid>
		<description>I&#039;d argue that in-site editing has another disadvantage.  If you have content/presentation separation then the author shouldnt really have to care where the content is being used, they should just be focused on making the content great.  By making the words flow nicely on their browser, on the one page where they are editing their content, does not mean it will work the same on every browser and every place where that content is in use (e.g. on a different device).

Personally I think that in-site editing discourages people to think about their content as a separate entity from the page in which it is displayed.</description>
		<content:encoded><![CDATA[<p>I&#8217;d argue that in-site editing has another disadvantage.  If you have content/presentation separation then the author shouldnt really have to care where the content is being used, they should just be focused on making the content great.  By making the words flow nicely on their browser, on the one page where they are editing their content, does not mean it will work the same on every browser and every place where that content is in use (e.g. on a different device).</p>
<p>Personally I think that in-site editing discourages people to think about their content as a separate entity from the page in which it is displayed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Robertson</title>
		<link>http://www.steptwo.com.au/papers/cmb_incontext/index.html/comment-page-1#comment-280</link>
		<dc:creator>James Robertson</dc:creator>
		<pubDate>Wed, 08 Oct 2008 21:30:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=106#comment-280</guid>
		<description>Definitely! I&#039;ve blogged on this just recently:

http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/</description>
		<content:encoded><![CDATA[<p>Definitely! I&#8217;ve blogged on this just recently:</p>
<p><a href="http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/" rel="nofollow">http://www.steptwo.com.au/columntwo/what-intranet-cmss-can-learn-from-wikis/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bèr Kessels</title>
		<link>http://www.steptwo.com.au/papers/cmb_incontext/index.html/comment-page-1#comment-278</link>
		<dc:creator>Bèr Kessels</dc:creator>
		<pubDate>Wed, 08 Oct 2008 13:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.steptwo.com.au/?p=106#comment-278</guid>
		<description>The author forgets to mention another case where in-context-editing is important: User Generated Content. Wiki(pedia), Digg-alikes, Facebook and so forth, all have no real backend for the day-to-day users. 
So, in the more modern approaches, where your site is a tool, rather then an exposition (where one can only read/consume) you are probably better off with an in-context approach.</description>
		<content:encoded><![CDATA[<p>The author forgets to mention another case where in-context-editing is important: User Generated Content. Wiki(pedia), Digg-alikes, Facebook and so forth, all have no real backend for the day-to-day users.<br />
So, in the more modern approaches, where your site is a tool, rather then an exposition (where one can only read/consume) you are probably better off with an in-context approach.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
