Overall Satisfaction with Plone
The slowprint.com public web presence has been on a Plone stack since SlowPrint started in 2007.
I also use Plone for other web properties, including my consulting at fraterdeus.com
As a content management system, Plone provides the ability to manage changing content requirements, for updating, adding new content, integrating a Twitter feed, etc.
I also use Plone for other web properties, including my consulting at fraterdeus.com
As a content management system, Plone provides the ability to manage changing content requirements, for updating, adding new content, integrating a Twitter feed, etc.
- Rock-solid technology stack. The python/Zope/Plone stack is as solid as anything else out there.
- Highly customizable TTW, if needed, via the Zope Management Interface, or Diazo XSL-transform theme design.
- Good support from core developers, lots of solid add-ons which address just about any needs.
- Amazingly customizable workflow, permissions and security management.
- Error messages are often cryptic, rising up with a traceback from deep in the system.
- It's perhaps hard to control this, since add-ons will always bring uncontrolled elements to bear.
- Perhaps some way to better visualize the source of the problem? End users should never see a traceback.
- TTW design options. In fact, Diazo based theming is remarkably powerful, and there are many tools for TTW design, but to better integrate this essential part of web development would make for a more useful end product.
- Positive in that we were able to launch a new site in a few days, mostly copying and pasting directly through-the-web from our old site.