Concrete CMS vs. Plone

Concrete5 is perfect for a website that needs to be regularly updated without accessing the code, whether that be because a developer created your site for you, or because you yourself are a developer who wants to keep the time spent on updates down.

In my experience, it's less useful for modern web apps such as PWAs that would benefit more from technologies such as React and Vue.

Incentivized

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.

• Concrete5 has a modular editing system, so you can edit the pages without having knowledge of coding. You just pick the module you want to insert or edit and click where you want it to go.
• You are able to edit modules in an HTML format if you would like to, so if you have the knowledge you can have even more control over your modules.
• You can also edit entire page themes by selecting them from the page layout menu. This allows you a greater versatility of the pages on your site.

Incentivized

• 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.

Incentivized

• Concrete5.6 websites have no good path to migrate to 5.7, short of manual content migration. This is a big problem and affected the user community negatively.
• Some features that were available as paid add-ons in 5.6, such as discussion forums and e-commerce shopping cart, are missing from newer versions 5.7/5.8.
• Starting to develop add-ons and customizations for Concrete5 can be challenging as 5.7/5.8 documentation is not yet complete.

Incentivized

• 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.

I have had nothing but good experiences with Concrete5. I have used it on several client websites and even several of my own sites. It is the leading CMS I will go to if I have a need to dynamically update content on a website by people who are typically untrained. They have solved every angst I had with the other solutions I have evaluated in the past and continue to be the simplest to implement and customize.

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

Although there is a slight learning curve (as with any software), it is very easy to use once you get a hold of it. It is easy to upload and manage files (and other digital assets), and the drag-n-drop interface on the front-end is easy for end-users to understand

Incentivized

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.

Since it's not tied to a central server (other than for authorizing updates and assigning licenses to specific sites), it's available pretty much 100% of the time.

Incentivized

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.

The site works extremely well, the front end flies, searches and form submissions are very fast indeed. The reason its a 9 not a ten? the back end can be a little slow at times, and this is unfair, because for the backend to be so amazing, it has to do a huge amount of work!

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.

Concrete5 is open-source and has an incredibly strong, polite, and supportive community. You can get an answer to nearly anything you want to do with Concrete5 by googling for it, searching the Concrete5 discussion forums or stack overflow, or posting your question to the forum. Members are very courteous and do not look down on those with less knowledge. And answers are always quick, informative, and supportive.

Incentivized

There are not too many Plone companies in the world. But the ones who are, are high level professionals

I have been participating Plone training and the trainers have always been professional. Materials were good and the instructions clear

Well organized, professional training with good materials and instructions

It's important that any CMS is implemented by a skilled developer. Content management is not a commodity. One of the keys I've found with Concrete5 is to create a homogenous content-entry method (e.g. focus on in-context editing OR focus on using the Composer feature). This seems to make it more likely that site editors will be able to easily come back to editing after a layoff without having to "remember" too much.

Incentivized

I didn't have to spend too much time learning Concrete CMS, whereas I had to spend a long time learning other CMSs. After struggling to develop a plugin for WordPress, developing an add-on for Concrete CMS was piece of cake thanks to many available APIs. Making custom themes and blocks was much easier than WordPress.

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.

Plone has no limits. We have massive sites and can run them just fine

• Even though the Concrete5 community is growing, it's still not up to the level as some of the other WCMS communities.
• More detailed statistics with historical data could be provided by the system.
• Concrete5 hihgly depends on Jquery. It makes it hard to upgrade the javascript library since the control panel depends on it.

• 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.