Re: when to implement a CMS and role of XSLT

Hi William,

I posted the following info a couple weeks ago.  It is relevant to your
query so I am posting the links again.  My approach was just as you
suggested - I created an XML grammar for XSLT content layout (I call mine
Web Page Composition Markup Language).  And then I wrapped a browser-based
CMS around this XML grammar. The CMS is a lightweight SOAP/WebDAV based
workflow engine on top of WPCML resources. I am looking for five
organizations interested in being test users of this framework (I have two
already so I can handle three more).  I would think that any CMS which
manages XML site resources could accomodate your content.  But I doubt the
CMS would know how to render it (i.e. how to run your XSLT pipeline).
-----------
Just a couple weeks ago I gave a presentation at the TRI-XML conference on
content management where I demonstrated a framework for generating pages
using a nested template approach. I had promised to make this presentation
available, so here are the links. The paper is at
http://www.activeinterface.com/thincms/thincms.pdf.  There is also a
PowerPoint at http://www.activeinterface.com/thincms/thincms.ppt.  Finally
there are several screenshots of a demonstration browser-based XML content
editor (see screenshot1.gif through screenshot5.gif at the same URL).

At 03:50 PM 8/22/2003 -0400, William Reilly wrote:


  ==============
  I'm curious what people on the list view as the role XSLT might play, in
  helping one "recover" from having to create a website once with no CMS
(but
  authoring all content in XML!), and then being later in a (reasonably
good?)
  position to transform what you have into whatever you learn your eventual
CMS
  is going to require.

--
http://cms-list.org/
more signal, less noise.