TheArchitect.co.uk - Jorgen Thelin's weblog
Enterprise technology for the real world.
Phil Wainewright makes some interesting comments about "Content-as-a-service" on the LooselyCoupled website:
This is all a bit of a departure for a content site, which according to conventional wisdom ought to be trying to suck in as much traffic as possible to its own pages. But I beg to differ. I think it's wrong to think of a website as a static destination. Better to think of it as a delivery hub, the point from which you disseminate information and services over the network on demand. All of this is part of a philosophy that I like to call "content-as-a-service".
[ Phil Wainewright - Post your news to our RSS feed ]
I encountered this change of emphasis too a few weeks back when I was chatting to someone from Vignette. He said there is a definite move away from trying to suck visitors in to a web site and get them to stay. So "stickyness" is now considered bad for web sites, and the new focus is on providing efficient access paths and navigation routes - so visitors can come to a web site, find the information or perform the task they need, and then depart quickly.
Lots of short, focused visits rather than a single long visit.
The obvious next step is enabling the repurposing of that underlying content by third parties, just as Google and Amazon have done with their content services, and all sorts of unexpected possibilities will emerge.
All content is
Copyright (c) 2010 Jorgen Thelin. All rights reserved.
The opinions expressed here represent my own views
and not necessarily those of my current, prior or future employer(s).
Content is provided "as-is", without any representations or warrenties of any kind.
Contents of the Weblog Feed are
licensed under a
Creative Commons License.
