Magnolia DXP - A very powerful and Flexible Digital Experience Platform
We are using Magnolia as the platform to centralized all our content and content production in one place. Leveraging on Magnolia's open …
Overview
What is Magnolia?
Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users…
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Page templates (73)8.989%
- Role-based user permissions (70)8.181%
- Admin section (71)8.080%
- Publishing workflow (74)7.575%
Reviewer Pros & Cons
Pricing
N/A
Unavailable
What is Magnolia?
Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users among brands like Atlassian and The New York Times, Magnolia…
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
44 people also want pricing
Alternatives Pricing
What is ExpressionEngine?
ExpressionEngine is a content management system from EllisLab in 2002, a successor to pMachine Pro, a blogging system, which is written in object-oriented PHP and uses MySQL for data storage. ExpressionEngine is their flagship Content Delivery Platform.
What is Adobe Business Catalyst (Discontinued)?
Adobe Business Catalyst was a cloud-hosted system for building and managing web content and online stores with a built-in CRM framework in addition to sales, service, and marketing features including eCommerce and Email Marketing tools. It has been end of life (EOL) since 2020.
Features
Return to navigation
Product Details
- About
- Integrations
- Competitors
- Tech Details
- Downloadables
- FAQs
What is Magnolia?
Founded in 1997 with a vision to create the first truly open content management system, Magnolia is presented as a fast way to launch digital experiences. With a mission to help clients move fast and stay flexible and boasting users among brands like Atlassian and The New York Times, Magnolia DXP supports industries ranging from automotive to telecommunications, offering enterprise features and headless agility to help them stay ahead.
From humble beginnings in Basel, Magnolia's footprint is now global with offices on five continents and more than 200 certified Magnolia Partners strategically located around the world.
Magnolia Features
Web Content Creation Features
- Supported: WYSIWYG editor
- Supported: Code quality / cleanliness
- Supported: Content versioning
- Supported: Admin section
- Supported: Page templates
- Supported: Mobile optimization / responsive design
- Supported: Publishing workflow
- Supported: Form generator
- Supported: Content scheduling
Web Content Management Features
- Supported: Internal content search
- Supported: Content taxonomy
- Supported: SEO support
- Supported: Browser compatibility
- Supported: Bulk management
- Supported: Page caching
- Supported: Availability / breadth of extensions
- Supported: Built-in e-commerce / shopping cart
- Supported: E-commerce / shopping cart extension
- Supported: Community / comment management
- Supported: Import / export
- Supported: Website analytics
Platform & Infrastructure Features
- Supported: API
- Supported: Internationalization / multi-language
Security Features
- Supported: Role-based user permissions
- Supported: User-level audit trail
- Supported: Version history
- Supported: Simple roll-back capabilities
CMS programming language or framework Features
- Supported: Java
Magnolia Screenshots
Magnolia Videos
The strengths of Magnolia in 100 seconds.
How to manage content in Magnolia more efficiently
Magnolia headless with no limits
Introducing the Magnolia Visual SPA Editor
Magnolia - Built for speed
Magnolia Integrations
- commercetools
- SAP Commerce Cloud
- Salesforce Commerce Cloud
- BigCommerce
- Bynder
- CELUM ContentHub
- Cloudinary
- Matomo Analytics
- Adobe Analytics
- Google Analytics
- Adobe Marketo Engage
- Adyen
- Siteimprove
- Elasticsearch
- RabbitMQ
- Apache Solr
- Oracle WebLogic Server
- IBM WebSphere Hybrid Edition
- Ehcache
- Memcached
- Microsoft Translator
- Spring Framework
- WildFly
- Adobe Commerce (Magento Commerce)
- Amazon S3 (Simple Storage Service)
- Translations.com
- GraphQL
- movingimage Enterprise Video Suite
- Salesforce Sales Cloud
- Netlify Platform
- Google Translate
- Bootstrap
- CAS
- REST APIs
- CommerceKit
- Biocryptology
- JBPM
- LDAP
- SiteMesh
Magnolia Competitors
Magnolia Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Linux, Mac |
| Mobile Application | Mobile Web |
| Supported Countries | Global |
Magnolia Downloadables
- DXP 101: From disjointed to seamless customer experiences - A beginner’s guide to Digital Experience Platforms
- Choosing a CMS for the Future of Ecommerce: The challenges brands face when attempting to deliver modern commerce experiences
- Reimagining Content & Commerce: Providing digital experiences for tomorrow’s customers
- Magnolia in a Can: Containerization with Magnolia
- Choosing a CMS: The Ultimate Guide - A step-by-step guide to finding the right system for your organization’s needs
Frequently Asked Questions
Adobe Experience Manager, Liferay Digital Experience Platform (DXP), and Acquia Digital Experience Platform are common alternatives for Magnolia.
Reviewers rate Page templates highest, with a score of 8.9.
The most common users of Magnolia are from Enterprises (1,001+ employees).
Magnolia Customer Size Distribution
| Consumers | 0% |
|---|---|
| Small Businesses (1-50 employees) | 10% |
| Mid-Size Companies (51-500 employees) | 57% |
| Enterprises (more than 500 employees) | 33% |
Comparisons
Compare with
Reviews and Ratings
(120)Attribute Ratings
Reviews
(1-1 of 1)Companies can't remove reviews or game the system. Here's why
August 20, 2015
Why choose Magnolia as Open Source CMS?
Magnolia CMS is a great product to develop enterprise websites, extranets and intranets. At the moment, the community is growing day by day but so far not many extensions are available. Magnolia is an enterprise CMS, the initial learning curve takes time, to learn all its functionalities and how to customize it is necessary to know Java. When one wants to develop just a simple website without complexity which doesn’t need any specific features such as workflow, versioning, environment separation between staging and public, etc. it is preferable to choose another CMS.
- The usability of Magnolia is appreciated, a content editor easily learns how to manage the content in two hours only.
- Magnolia is open, flexible and extendible and it is possible to modify or improve the standards features. Using Java API, REST, SOAP, CMIS, XML, etc. makes it possible to integrate other software or legacy data.
- Magnolia as a modular architecture, a module has its lifecycle, configuration, version handing and dependency: this is a good approach for package content and functionality.
- Magnolia is written in Java, the platform of choice for enterprise IT systems. It is scalable, stable and secure, and Magnolia separates the staging from public environment.
- Magnolia lacks of an administrative dashboard showing all the workflow, possibly in a graphical representation of their status.
- The audit module only logs in a file: having a dashboard for the audit would be a nice improvement.
- When the time comes to configure templates and components in the Standard Templating Kit is quite complicated and boring at times. A widget to help the developer would be a very interesting job. In addition, having the possibility to configure template and component in the Standard Template Kit by code would be nice.
- Implementing a customization in the administrative UI or in the dialogs isn’t simple and the developer must know Vaadin.
- Migrating from the previous major release is complicated and expensive, since Magnolia 5 isn’t compatible with the old major versions (Magnolia 4).
- The biggest business for Tinext is digital marketing. Our team - which includes Sales accounts, Project managers, information architects, software engineers, designers, system engineers, etc. - use Magnolia CMS every day. Having a team focused on a product only is very efficient and allows us to offer a good service and advice to customers.
- Our customers have very high expectations and need a lot of integration: the flexibility of Magnolia allows us to satisfy every request.
I evaluated many CMS products and I’m continuing to evaluate them to verify the new functionality introduced.
I evaluated these products: Alfresco, Apache Lenya, DotCMS, Drupal, Liferay, Hippo, Joomla, OpenCMS. I chose Magnolia because Magnolia offers two licensed community editions and the commercial edition, is written in Java, the solution is open and extensible, it is very simple to use for the contributors, and includes a good set of functionalities out of the box, as well as being secure and scalable. I think Alfresco is a very good DMS but the CMS functionality could be improved.
If I had to develop a portal with portlet I would choose, but the portlet needs a lot of system resources, as well as the integration of the external product or legacy data which usually doesn’t support natively the portlet so I haven’t used Liferay in a real project. Apache Lenya, DotCMS, Hippo and OpenCMS are very good products too, especially Hippo CMS which in the last few years made important improvements. Drupal and Joomla are very simple to use and to develop a small website, and there are many extensions available in the community. On the other hand, customizing or integrating other systems is not so simple.
I evaluated these products: Alfresco, Apache Lenya, DotCMS, Drupal, Liferay, Hippo, Joomla, OpenCMS. I chose Magnolia because Magnolia offers two licensed community editions and the commercial edition, is written in Java, the solution is open and extensible, it is very simple to use for the contributors, and includes a good set of functionalities out of the box, as well as being secure and scalable. I think Alfresco is a very good DMS but the CMS functionality could be improved.
If I had to develop a portal with portlet I would choose, but the portlet needs a lot of system resources, as well as the integration of the external product or legacy data which usually doesn’t support natively the portlet so I haven’t used Liferay in a real project. Apache Lenya, DotCMS, Hippo and OpenCMS are very good products too, especially Hippo CMS which in the last few years made important improvements. Drupal and Joomla are very simple to use and to develop a small website, and there are many extensions available in the community. On the other hand, customizing or integrating other systems is not so simple.
12