Hassan Schroeder wrote:
Geoff Deering wrote:
One of the whole problems with text area editing, just adding text and
basic formatting, is; how do you present an interface to the user to
markup the structure of the content correctly; headings, lists,
paragraphs, tables, etc?
I would suggest that a real CMS doesn't have anything to do with
HTML, or any other specific output format :-)
Content will be *semantically* collected and stored *without any*
consideration for the eventual output form.
The CMS implementer creates the data collection forms to match the
*data* to be collected, as well as output transformations for the
target format (HTML, PDF, whatever).
Make sense?
Sure, that makes sense, but where do you find this CMS?
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. 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.
But there are still many problems with this, even though it is the best
approach for organisation based web sites (or at least sections of them).
-----------------
Geoff Deering
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
