Acquia Digital Experience Platform vs. Magnolia

It made it super easy to upgrade 300+ Drupal sites to the latest major version in 12 weeks, end to end. It is easy to deploy legal changes and updates to components at scale. Turnkey service to deploy new environments and to clone sites. There are no ecosystem lock-in principles for Customer service/success services and professional services for new approaches.

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

• Acquia keeps the site up and available. I don't think we've had a second of downtime caused by Acquia.
• Their administration UI makes it pretty easy to manage the websites at a high level. Check stats, change key configuration values, backup code and databases, manage SSL, create support tickets and manage development teams (users).
• Their support team can do performance reviews of your website and give you tips for improving performance.

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

• the support portal can be hit and miss. sometimes there are very helpful people who get back to you in a timely manner, but more often there's a lot of lag time for the ticket to get picked up and in between responses, which can also be less than helpful.
• it seems like the different departments within acquia (support, management, build teams) don't communicate with each other.
• because features are so dense and granular, sometimes the workflow or how they are connected can be really complex to access.

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

We're moving away from Drupal as a platform. Drupal 8 and 9 were simply too overburdened and difficult to maintain compared to other offerings. PHP seems like a dying language so we are currently in the process of migrating all of our Drupal 7 functionality and custom modules to a Python/Django/Wagtail platform. This doesn't mean Acquia isn't a great service, they are professional and top-knotch, but the only way we'd say with them is if I didn't complete the migration.

Incentivized

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.

It's a great user interface. It's always being updated and I've never noticed a bad update that increased the complexity or reduced

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

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

Every time we have had an issue, Acquia support has responded promptly and worked with us as a team to solve the problem. The Acquia support team is global and we have literally had interactions with all of their support offices, yet the experience has been the same - top notch

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 was implemented when I got there. I don't know how it was prior.

Incentivized

We chose Acquia for a much better UI that gave non-analytical marketers and easy to use tool where they could create their own reports. The campaign side of things also had an easier to use UI as well, that made the targeting of audiences much easier.

Incentivized

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)

The DXP tools can handle millions of requests and can scale automatically to fit your needs. We have clients that use only part of the DXP tools and have a small usage, but even in these cases they see great value in using tools like personalization and CDP.

Incentivized

• A reliable platform = happy user base!
• Ours is a non-profit service, we are happy that people appreciate and recommend the site for its content.
• FLEXspace.org rapidly grew to over 6,000 users from 1,400 educational institutions across 75 countries - it is a joy to watch educators contributing content and sharing ideas.

Incentivized

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