1. 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.

  2. Wilf

    I’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.

Leave a Reply

Your email address will not be published. Required fields are marked *

Published April 7, 2008

James Robertson
James Robertson is the Managing Director of Step Two, the global thought leaders on intranets, headquartered in Sydney, Australia. James is the author of the best-selling books Essential intranets, Designing intranets and What every intranet team should know. He has keynoted conferences around the globe. (Follow him on Twitter)

Related Posts