Zope is greate, all reviews say so. Most of the reviews complain the documentation. I believe all come to known zope have experience the same difficults and all those remains can feel the power of zope. Not only the documentation is matter. Under the greate architecture, zope is inconsistance, non-intutive, and mistiness. To be fast to market is not enough, it must also easy to maintain, endure greate and fast change to make zope success. To make good use of zope, one should paid more attentation on content instead of control. Making separation of control and content as deep as possible. Write re-usable, structural components. I believe the following is very important : 1. re-introduce unified naming convention. encourage developers to change over this 2. move un-necessary codes from the zope kernel to user space: <base> <lang> ... 3. support of unicode 4. make zope content easy to co-operative with current technonlgy especially search engines. zope oodb is greate, but it prevent other apps to access the data, so it is difficult to contruct a local search facility. 5. support cvs style versioning 6. multiple output format 7. new scripting language, encourage separation of content and control, may be more xsl and xpointer style. Converting zope to Jpython have the following benefits: 1. Unicode support 2. draw other java components : for example, several xml tools being develop in Apache.org is very useful. If a complete re-write is not economic, at least DC should consider how to separate the content and control in zope, make the syntax easy to learn and use. Rgs, Kent Sin