Re: Standard list of WCMS features

I am just speaking in terms of

- usability
- ease of use
- ease of building usable solutions for differing users
- integrating with the rest of infrastructures

I have looked at NetDoc and that is not what we are looking for.

We are looking for toolkits and solutions which we can use to build 
specific solutions for specific clients with excellent charateristics.

At times, solutions are not mature. Sometimes, you wait and see if it 
matures.

I would have to say Plone made that possible for Zope. Opening up 
how-tos and APIs and creating a core group of developers who had 
multiple CMS implementations under their belts.

Zen of Zope ---> Plone
Zen of Plone ---> MA-lle-ABLE

I think other systems do learn and can do better from coming in contact 
with Zope/Plone. In other words, Zope simply defies characterization 
because of its diverse developer community.

Ilkka Huotari wrote:

>>Also, it is never the issues of which CMS but how you use it. Some CMSes
>>are good to build simple pages like NetDoc and some CMSes care more
>>geared to do HEAVY lifting.
>>    
>>
>
>Thanks fo noticing :)
>
>I think you are talking about scalability here, right? That is, if the site
>contains thousands of pages, how does the CMS handle it.
>
>I think the simple concept of hierarchy goes a long way here - at least for
>the site structure and the way the CMS stores the information.
>
>Workflow may be another matter though.
>
>--
>Ilkka Huotari
>Netdoc - http://www.visiomode.com/
>
>  
>


-- 
Chalu Kim                 “Digital cooperative”
eGenius Inc, 20 Jay Street, 1002, Brooklyn, New York 11201
(718) 858-0142, (718) 858-2434 (fax)