it's maybe not that bad as i said before, but still i see zope.org as one of the biggest black spots in zope world.
for now i really dont like this blog post, mostly i complain, makes me feel like my friend's wife. well i guess it would be nice to write some solutions for this problem:
- show more clearly that zope (3) is going more python way, i really like plone.org first page and that tabbed presentation of plone. it gives visitor quick overview of plone. zope should have some similar quick presentation of what zope can do.
- documentation should be better categorized. so you could quickly found all the documentation/tutorials/howtos about you problem. there should also be a mark for outdated documentation. i'm also missing commenting on howto's.
- i think there should be a section totally devoted to WSGI. here i mean middleware of all kinds. repoze.org ppl should be in-charge of that section. they are doing excellent work. all in all wsgi is pythons web future.
- ok also some design work should be done, so its more clear and user friendly to use, but hey, thats only my opinion.
in short that would be it ... maybe i'll come up with something tomorrow, but i would really like to hear what all other zope (ab)users think about zope.org. was there already some discussion about this that i missed. i just recently (last 3 months) subscribed to zope, plone planets so i should maybe not judge this.
1 comment:
I think this caught my attention because it showed honesty and courage to identify weaknesses in the Zope framework. thanks for the information.
Post a Comment