RE: Dynamic CMS Publishing?

Ian Kallen wrote:
> in general, editorial content and user data should be managed
separately.

Interesting. Any other thoughts on this? I deliberately don't
distinguish users from admin users or user submitted data from
editorially submitted data. 

Why? Firstly, for simplicity - I only have one user login/authentication
system and one admin system and I use the admin system (which is
accessible in-page, in-site or through an external admin site) for every
user input. I also only have one security system allowing any set of
security permissions for any pages, content types, content instances,
etc.

Secondly because I think there is that it's artificial to distinguish
users from admins. For example, while filling out a "contact us" form
seems quite different from adding a new article to the home page, what
about submitting a thread to a discussion group, a review for a product,
or even adding your own single page home page in a "community" section?
Sure sounds like administrative tasks to me! As sites become more
interactive, I think that the clear distinction between visitors and
administrators will continue to blur. 

Also, from a technical standpoint, treat each form as an object type
(like a page, user, article or product), and a single system can be used
for displaying, processing, validating and creating workflow based on
form input whether the form is a "contact us" or a "add new page" with a
single set of auto generated repository management stored procedures
handling the data access. 

Any thoughts?!

Best Wishes,
Peter


---
[This E-mail scanned for viruses by Declude Virus]