Concrete CMS vs. Magnolia

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

If you need a business CMS that brings along a good amount of features and also give you the chance to develop features on your own, Magnolia would be a good choice. Even if you have not the fitting infrastructure around, Magnolia provides you different ways like SAAS oder PAAS. If you have to review your code our have any problems the team behind will helps in a short time. Without using the connectors it is not so easy to connect special functionalities like Marketing tools or optimization tools. The DAM is very slow if you have an huge amount of documents and pictures to store for your website - you have to add an external DAM.

Incentivized

• 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

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

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

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

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.

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

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

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

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

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!

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

Incentivized

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

You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases

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.

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

• 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 have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.