return to Plone for the second time.

still remember last time i learn Plone, and turn out it's way too complicated for me. after one week study I gave up with disgust and even had no idea of what Plone can do?

later, i find Django, which is really simple and elegant. and it turns out to be very productive indeed. I must say i like this framework very much. 

this time i pick up Plone again because my company is engaging a deal using Plone. with so many good words you can find on web for Plone, i reconsider to make a further research on Plone again. here listed my overall initial impression.

1. learning curve is extreamly high. even with a lot of CMS experience on other platform such as Documentum, Vignette etc, it's still very difficulte to learn. 
2. if you are making a heavy interactive or personalization site (like web2.0 sites). Plone may not help you much. Plone turns out to be very useful in the sites which is in some extent look like static, such as a newspaper site. 
3. it's true you can find may adds-on products, but don't take it for granted that you don't need to write code any more.  because not only the quality of the adds-on products are not guaranteed, but they are unlikely to meet your requirement totally. 
4. ZODB is a mystery. since most of you are from SQL camp, you should have the idea of security, performance, backup, maintenance etc of SQL. it's true SQL DB itself is very complicated, so you should expect the same way in ZODB. 

so in short. i feel, if you are doing project which is uncritical (such as POC or small site with less interactive from user) or you do want those out-of-the-box functions provided with Plone and no further customization is requried, then you may choose Plone. Otherwise, I think you should choose some other agile web framework like Django.