[Sigia-l] Client's web worldview [was CMS and IA]

[Laura Norvig]

OK, this thread is very timely as I am immersed in my first migration 
project from a static site to a CMS. The very first thing I noticed 
was the ease with which an article can be published in different 
spots - difficulties arise more when one tries to force the old 
static model onto the new dynamic one.

-Laura

Luca Rosati wrote:

>  > Following on from Peter's comments, three things that I
>>  have noticed while working a CMS.
>>  * Separating out where a piece of content (content object)
>>  is placed or published to from the object itself, so it can
>>  live in many places or platforms. Therefore not creating a
>>  "an article for the Music web site", but an article that is
>>  about music and can be published in many places like the
>>  Music web site, a Going Out section of a site or to
>>  interactive TV.

Jon Hanna wrote:

>Hmm. I've resisted the urge to either say "we do that" or else defend our
>not doing something so far in this thread, but in this case I'm lead to
>another question. We do indeed have this notion of content objects being
>separated from a given use, however it's something that clients and
>prospective clients don't seem to "get".
>
>No big loss for us as a company, we can facilitate the other way of doing
>things, so we can still get the sale, but as a developer of the system I
>find it a bit annoying personally that this way of thinking isn't much used.
>
>So the question is, what is the best way to get clients' worldview of the
>web away from the rather static "sites with articles" view? Or should one
>bother if the client is happy as things are? Or is that for their IA
>consultant to do while we just build their software? :)