Plone is a free and open source content management system built on top of the Zope application server. Plone can be used for any kind of website, including blogs, internet sites, webshops, and internal websites.
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and …
We haven't have any need for other CMSs since 2004 when we first started using Plone. There hasn't been any feature or request or system that we couldn't have done with Plone, if that was the platform selection in case.
Plone is really almost the only truly enterprise opensource CMS. Most of its opensource competitors cant compete in this area, while they may have some nice editing tools, and some cool features, Plone stands our for its security, scalability, version control, highly …
Plone is much harder to learn then Wordpress. Development in Wordpress is learnt in day's, where development in Plone really takes years to get to the full depth. That said, once you're able to develop in Plone, is it a rock solid system, with readable code. In my experience …
Among the open source CMSs Plone is most reliable to develop large and complex application because is codebase is maintained with an object oriented approach where each parts is strictly independent from the others. So you can deeply customize it and it is still secure and …
The security is much better with Plone than most of its competitors. It is also written in Python which makes it a better target for internal software development than PHP (which as a language is quite broken). Plone's component architecture makes our own extensions more …
Plone may be more complicated than Wordpress when considering organizational factors and overall use, but for a reason. It has further capabilities than Wordpress and other content management systems. It takes slight training to learn, but it provides great knowledge that many …
I did not select Plone. It was the choice of the organization we were doing the contract work for. I did not look into other products.
Verified User
Team Lead
Chose Plone
Plone is highly customizable as are the products above. But Plone offers many other design features and standards which others don't. Plone also has the largest open source community providing new modules and ideas for you to add to plone.
The larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.
Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
Plone is secure. It is the most secure CMS you can get your hands on.
Plone is flexible, and makes fast development easy.
Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).
I no longer use Plone because I got an internship in the web development field and my current place of employment uses their own content management system that they created. After getting to know other CMS's and similar software and comparing them to Plone, I would enjoy using Plone again in the future, but there are more complicated software that I'd like to learn as I progress in my field of study.
Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small
Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.
Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better
As a development company Plone allows us to provide complex web applications in a short amount of time.
Plone is quite robust and reliable so when you customize some parts you do not risk to damage other parts. This is quite positive for a web development framework,
Plone allows our clients to spread their activities among different employees improving the efficiency of content generation and management.