Geoff Deering wrote: > Sure, that makes sense, but where do you find this CMS?
As I mentioned, Interwoven TeamSite for one (which I've had a bit of experience with). > I think only Lenya/Axkit and Forrest have an architecture that addresses > this, and also "Transit Central" and "Knowledge Tree". But watch the > Forrest mail list and see the pain that people go through to skin their > apps. It's not funny. I've only fiddled with Lenya a little, not actually deployed it, and no experience with Forrest. OTOH, it seems simpler to me to just create a schema (XML or DB) and write the input forms and output transforms for a particular application than to implement someone else's one-size-fits-all solution. > But I feel that this is the correct approach; to > be able to put Word/OpenOffice docs into the directory structure and the > application transform them into whatever document the system targets, > through XSL or similar approaches. Actually, that's not what I was referring to -- *no* Word doc I've ever been given to convert to HTML manually has been formatted in any kind of semantic way. The approach I'm suggesting is to acquire the content with as high a degree of granularity as possible. Look at something like the DocBook (or Simplified DocBook) schema and imagine creating a form to input that level of detail for a publication. Though not necessarily each item -- even Simplified DocBook is huge, and at some point the content providers revolt and storm the castle with pitchforks and flaming torches. :-) -- Hassan Schroeder ----------------------------- [EMAIL PROTECTED] Webtuitive Design === (+1) 408-938-0567 === http://webtuitive.com dream. code. ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
