Concrete CMS (formerly Concrete5) is a free and open source, PHP built content management system for content on the web and also for intranets. It is optimized to support the creation of online magazines and newspapers.
N/A
Optimizely Content Management System
Score 8.6 out of 10
N/A
Optimizely Content Management System (CMS) is purpose-built for marketers, and fully composable for developers. The CMS supports the end-to-end content lifecycle, helping users to deliver on-brand, high-impact digital experiences that 'wow' audiences.
N/A
Pricing
Concrete CMS
Optimizely Content Management System
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Concrete CMS
Optimizely Content Management System
Free Trial
No
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
—
More Pricing Information
Community Pulse
Concrete CMS
Optimizely Content Management System
Features
Concrete CMS
Optimizely Content Management System
Security
Comparison of Security features of Product A and Product B
Concrete CMS
9.5
Ratings
16% above category average
Optimizely Content Management System
8.5
Ratings
5% above category average
Role-based user permissions
9.50 Ratings
8.50 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Concrete CMS
9.7
Ratings
24% above category average
Optimizely Content Management System
8.0
Ratings
5% above category average
API
9.70 Ratings
8.10 Ratings
Internationalization / multi-language
9.70 Ratings
7.80 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Concrete CMS
8.4
Ratings
8% above category average
Optimizely Content Management System
7.9
Ratings
2% above category average
WYSIWYG editor
9.30 Ratings
7.80 Ratings
Code quality / cleanliness
10.00 Ratings
8.30 Ratings
Admin section
10.00 Ratings
8.20 Ratings
Page templates
10.00 Ratings
8.40 Ratings
Library of website themes
4.20 Ratings
7.50 Ratings
Mobile optimization / responsive design
9.70 Ratings
7.90 Ratings
Publishing workflow
7.70 Ratings
8.20 Ratings
Form generator
6.60 Ratings
6.90 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
Very much if a business is doing a rebrand, for example, or a digital transformation, the DXP product is super competitive. The managed services that provided around the infrastructure and all of the moving parts really, really works well. It just makes life as a developer very easy when ultimately you just have to do the code and deploy it out and don't worry about the environment infrastructure. I think it's really, really well and fits in really well with that. Areas where it's not so great in my experience, I would say, well, I've already mentioned kind of the CMS to SaaS product, but also just in general it feels like we're going through a bit of a transition period with the documentation at the moment. So when new features are rolled out or the product catalog expands, the documentation isn't always the best or streamlined. That can make life as a developer a little bit work at the times.
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.
Folder structure - I was on Magento 1.x & 2.x for 10 years, which had no folder structure for blocks or images - it was very difficult to find things. We couldn't keep anything straight without it.
The fact that it knows what block or image is being used and links to where it's being used is pure gold. It prevents deletion of needed elements.
I like that I can drag a block or image somewhere new and it doesn't break anything.
Our search of blocks and images is now working, that's very helpful.
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.
promo types, several have been released that do not work as they are advertised/labeled which has caused us to make custom promos for just about all of them where we've actually fixed the functionality. The OOB types are completely unreliable
promo exclusions/sorting -- this is very buggy, and some of this would normally be "out of the box" like no two order discounts should ever be able to stack. This gets incredibly difficult to manage when you have 75 active promos at a time.
asset management - replacement files with same name aren't recognized even when the first version is deleted, this creates a mess in asset folders - nothing can be successfully deleted from epi asset library
html automatic edits -- issues when typing in either content page links or asset links, epi always adds random characters to the end (?"Epieditmode=false,6789" for example, which doesn't break content, but does make it more difficult for the team to use non-epi html tools to build or edit
auto dimensions on images -- when adding an image in the html, you have the address exactly, but any other way causes the editor to put width and height dims on the code, making the image warp in mobile, this is adding steps to undo the automatic edits, they are completely unhelpful
blogs - we are running a blog in Opti that is compeltely manual, every "related article" and every "articles about x topic" block is hard coded, there is nothing dynamic in the content library which is frustrating, and creates a huge time suck for articles across the site, every time there is a new one, that's 10+ manual page updates
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.
Since I work on the implementation side of things, and do not directly own licensing for Ektron CMS, I have to base this rating off of how I think it will be received or presented to customers looking to start a new site deployment. I try to remain CMS agnostic, though my specialty is with the .NET and Microsoft stack. Because of the experience I have working with Ektron, I tend to be more forgiving with the shortcomings as I am familiar with how to work around them or past them from experience. Being familiar with the community available also helps, as you become familiar with the best approaches to find solutions to your issues. Each product has it's ups and downs and all of them are only going to be as good as the company or development team implementing them can make them. This is EXTREMELY important to remember when choosing a CMS, as it can make or break your expensive investment.
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
From our editors perspective they find the CMS system easy and to clear to use. Our developers find it very easy to design on and appreciate the level of service support available. It's also always evolving and getting better every year. We find this investment reassuring and encourages us to try keep pace and see how we can continue to push the envelope and continue to improve all aspect of our websites and online touch points.
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.
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!
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.
I attended multiple trainings/tutorials early in the process. The vendor-supplied content about Optimizely was engaging for users/attendees (I often analyze training content, compliance programs, governance plans), which helps our OCM people by having good "word of mouth" about the product long before a rollout ever happens. I actually when the user-focused portion of the Optimizely Academy twice in 2022 to ensure I had a grasp on operability and to be able to support the training and OCM efforts
Ektron is one of the best solution for .Net platform. Over the years have improved the performance issues that the previous versions had. My only complain is right now you can't do Page builder pages if you choose to have a MVC architecture
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.
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.
Optimizely Content Management System takes the best bit of previous platforms and simplifies them without removing the more advanced features but not making the necessary to get things going. allowing for any user to jump in and start working is a massive help but empowering power users to take advantage of all its features.