Re: Cross-platform, device independent CMS

Daniel,

It's great that we're making progress here.. the terminology and references
you use make sense to me and I'm confident we're on the same wavelength.

Now, with regard to the CMS itself.. yes, I agree on a number of your
points.. perhaps even all of them. The problem is with implementation. So
far, just about every CMS I've come across claims to offer a great deal of
presentation flexibility, and yet the actual "nitty-gritty" of delivering
these rich DHTML, CSS-heavy SQL-driven behemoths to a lowly WAP browser to
the extent to allow secure transactions is beyond what most CMSs are willing
to defend, let alone boast.

In short, how tall a mountain is this we're climbing? Where can I read up
about this... preferably with working demonstrations for use with a few
major market segments: lynx, wap, PDA, GUI.. and secure if/when possible. If
I'm going to invest time and energy into someone else's product or package,
I need to know how much easier it would be than coding it myself!


Thanks, again,
Julian.

p.s. Sun Toft & Plone, your comments too please!

----- Original Message ----- 
From: "Daniel Iversen" <[email protected]>
To: <[email protected]>
Sent: Thursday, November 25, 2004 6:09 PM
Subject: [CMS] RE: cms Digest, Vol 10, Issue 12


> Hi there Julian,
>
> I might agree with Darrel and say that the requirement of ubiquitous
> access
> to web-content can be addressed in different ways and at different levels.
>
> While flexible template coding will bring you some of the way it will most
> likely not solve all your delivery requirements and having only predefined
> destinations such as wap,web,etc. is a bad idea as well as it leaves you
> inflexible for future requirements.
>
> What you want/need for content accessibility/delivery is a CMS that meets
> the following requirements:
>
> * Gives developers free hands in terms of templating
> * Different Publishing mechanisms (generating static files or dynamic
> delivery)
> * can set headers/mimetypes of your content! (important but tricky
> requirement - for example to set content type to "text/vnd.wap.wml",
> "application/rtf" or "text/hdml" instead of only "text/html")
> * integrates with transformation engines (to create word doc, pdf's etc)
> * "cleans up" data in the content aggregation/contribution process (i.e.
> strips out the proprietary tags in MS Office HTML documents)
> * Stores data in the most raw form - preferably in the database for
> maximum
> manipulation.
>
> I represent FatWire Software in Australia and our CMS (Content Server) has
> the above capabilities (and so does a few other).
>
> Kind regards,
> Daniel