RE: the relationship between CM and IA(information arc hitecture)

Drew Volpe <dvolpe-jiiSg/XTN8tWk0Htik3J/[email protected]> Wed, 24 Dec 2003 10:57:37 -0500
Newsgroups gmane.comp.cms.general
Message-ID <[email protected]>
> -----Original Message-----
> From: Austin, Darrel [mailto:[email protected]]
> Sent: Wednesday, December 24, 2003 9:58 AM
> To: cms-list-/[email protected]
> Subject: RE: [cms-list] the relationship between CM and IA(information arc
hitecture)
> 

> 
> I don't think the relationship between CM and IA should really be that
> close. CM is specific to the content, IA is specific to the presentation.
> You may very well have multiple IA layouts for the same content, depending
> on how/where you are delivering your content to.
> 
> In my limited experience with CMSs, one drawback to some of them is that
> they tend tie the content into a very specific web-based IA. It makes the
> assumption that any content you enter into the system will likely be
> delivered to one specific web site. At that point, any relationship
between
> the CM and IA just tends to get in the way.

I would agree with this, but I think it's changing and won't be the
case in a few years.  People are realizing that their website is a subset
of their larger content management problem.  The web is one of many
delivery methods and by combining all content together it's much easier to
reuse content and, in general, manage everything.

I think there were be a shift to CMSs which hold the content alone
without any presentation (in XML) and which then publish content into
a variety of formats, including HTML but also things like .chm and pdf.   
It just doesn't make any sense to have web content stored off in a separate,

disparate respository, and CMS designers are realizing this and moving that
way.


dv
--
http://cms-list.org/
please trim your posts.