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.
N/A
Squiz Digital Experience Platform
Score 5.2 out of 10
N/A
Squiz Digital Experience Platform (DXP) is a platform for creating websites, personalized journeys, and optimized experiences. Its marketing tools support content management and on-site conversational search, personalization, forms, and integrations to build and optimize intelligent sites.
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 …
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 …
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 …
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 …
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 …
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 …
Verified User
Anonymous
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.
Bullets and formatting sometimes make it difficult to add text to an existing paragraph. The 'code' button is useful in those cases, but only to those who know html.
Sometimes the pages don't save correctly and you use information.
Uploading and displaying images is a bit too much work.
Plone has been used for more than ten years and it already has an interesting roadmap for its future. I do not know any other open source CMS with the same story of continuous evolution and security track. Interesting new features are added at each release and new modules are created continuously
I don't work with Squiz any more so it's difficult to say, that said, the site is still running on the same CMS so obviously it's still considered a great platform
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.
The new user interface in Plone 6 is even better, it is super fast, has lots of different blocks for enhancing the page, has flexible layout system and is easy to extend with more features.
Our Plone sites are very robust. We have critical systems on Plone and we have been running sites on Plone for over 20 years with very little unexpected downtime.
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.
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 Wordpress websites need to be updated so often, and the code feels bad organised. I have been building Wordpress websites, choosing Wordpress only when the client has almost no money. But I can never deliver the quality I want to deliver when using Wordpress. Plone does offer the possibility to deliver professional websites. As for Joomla, in the past I have done some Joomla development, but the whole CMS-paradigm could not settle in my brain. Being a web developer for over 15 years now, Joomla always felt contra-intuitive. Let alone the task of teaching this to my clients. Plone is now my only choice. It gives me a fast development-cycle, a user-friendly CMS and a rock stable and very secure system.
We thought that tapping into the user/content management tooling of Plone would be a good and useful thing, however it turned out to be a major pain to tie into those parts of Plone.
I wish we would have built the extra functionality completely outside Plone and found a way to integrate it. It would have been much easier.
Having a single powerful CMS platform that would integrate a number of organisations that had recently merged - Squiz was a big part of bringing our web architecture together gracefully.