This query started out in a separate thread about permissions, but it's
sufficiently important to me to pose again here.

I've been struggling to make the CMS abilities of zope user-friendly enough
for 'joe average' end-users.  Really it's designed for a 'power' content
manager who delegates, secures, and generally has taken the time to study
all the Content Management docs, etc.  However, most of my clients don't
have those kinds of requirements and aren't that technologically savvy, so I
end up coding ultra-simplified interfaces for them on a per-project basis.

I know you can restrict permissions on just about every available method,
and I am aware of the current skinnable zope project, which may improve the
situation drastically.  But I'm interested to know, how many of you offer
the Zope TTW interface to clients as a content management system, and how
many just use it as a development interface?  I'm beginning to wonder if
content management and system administration should be split out into
separate subsystems.  Or if a CMS Tool Kit should be developed.  (workflows,
syndication, etc...).  But I'm still far from being a zope power user
myself, and have yet to appreciate the range of its potential.

What do you people think?


Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to