> Someone has already done something of similar?

SmallWiki has got a similar approach of serving-web pages. What you call 
in Zope a 'type' or an 'application' is called 'structure' in SmallWiki. 
Right now, as its name suggests, the available types are targeted for 
wiki and content-management: Folder and Resource are exactly the same as 
in Zope, Page is more like a ZWikiPage. Even some special structures 
have been written some time ago, like a Photo-Gallery, a Keyword-Index, 
a Link-Collection, etc.

I have to admit that I did work a lot with Zope a few years ago, 
therefor you might discover even more similarities, like the Security 
management and the look-up of urls. On the other hand, SmallWiki has 
also taken some ideas from Seaside, like the html-rendering and the 
possibility to perform callbacks with links and form-elements.

A documentation of SmallWiki can be found at:

	http://www.iam.unibe.ch/~scg/smallwiki/smallwiki.pdf 

> What do you think of Zope?

- I do not like to work with request and response directly, this is too 
low-level to build real applications. Seaside and SmallWiki both have 
nice concepts to avoid working with header-fields.

- I do not like the management-interface of Zope: it is slow and does 
not work properly with all browsers. Furthermore it is impossible to 
find references to and from other places in the code, something that 
every Smalltalk IDE is providing.

- I want to debug/test my code, but Zope doesn't allow (out of the box).

- ...

By-the-way, Zope has been designed by a former Smalltalker. He choose to 
go for Python as he thinks its syntax is cleaner and the multiple-
inheritance is missing. Ohh boy, ... :-(

To read a full report on this see:

	http://www.zopera.org/Members/odeckmyn/fulton_iv_2002   

Cheers,
Lukas

-- 
Lukas Renggli
http://renggli.freezope.org