Hi Steve, Rex,
This thread is close to my heart and Steve, I think Rex has a point. I've
been doing a lot of research recently; I hadn't done the round in about a
year. I don't know why I never noticed but there is a MAJOR rift in system
architecture that Rex is alluding to. A CMS IMHO *must* be able to manage
content _internally_ before any template has been built - ie. framework. I
was taught that CM means having, as Rex said, tools that let you manage a
core of structured content that can be intelligently exported any way you
want it. I can't find a written down definition for you Steve but that's
the idea. I've been surprised at the number of systems that don't do it.
Question for every vendor on this list: Can you create content without a
template?
a.
PS. Good call Rex.
PPS. My first post to this list like a year ago was about content
management frameworks. I never understood why I didn't get much of a
response.
Andr� Milton
www.mlore.com
-----Original Message-----
Behalf Of Steve Williams
"A true CMS should only be dealing with content management and not with
presentation.
ie. It should provide tools that let users update and manage content easily,
eg. Submitting word doc, versioning, workflow."
Rex - I would love to know where it written down what a CMS can and cant be
?
--
http://cms-list.org/
trim your replies for good karma.
