Skip to main content
TrustRadius
Magnolia

Magnolia

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…

Read more
Recent Reviews

Magnolia CMS

10 out of 10
March 30, 2024
Incentivized
Magnolia is our front end CMS serving the content for our B2B website serving 24 countries and 18 different languages. The Magnolia CMS …
Continue reading

Personalisation is key

7 out of 10
October 16, 2023
About 3 years ago we looked at updating our CMS solution to something that was more adaptable and allow us to be more personalised with …
Continue reading
Read all 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

View all 16 features
  • Page templates (73)
    8.9
    89%
  • Role-based user permissions (70)
    8.1
    81%
  • Admin section (71)
    8.0
    80%
  • Publishing workflow (74)
    7.5
    75%

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all 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.

Return to navigation

Features

Security

This component helps a company minimize the security risks by controlling access to the software and its data, and encouraging best practices among users.

8.1
Avg 8.0

Platform & Infrastructure

Features related to platform-wide settings and structure, such as permissions, languages, integrations, customizations, etc.

8
Avg 7.7

Web Content Creation

Features that support the creation of website content.

8
Avg 7.6

Web Content Management

Features for managing website content

7.5
Avg 7.3
Return to navigation

Product Details

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

Screenshot of the customer experience: Brings together content and audiovisual digital assets to form more compelling digital experiences.Screenshot of the Magnolia App Launcher, used to switch between workspaces and manage pagesScreenshot of Magnolia's native analytics integration framework, used to take advantage of data directly in the authoring UI, coupled to content.Screenshot of global search that brings relevant content, no matter where it resides.Screenshot of customizing the ecommerce experience.

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 Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux, Mac
Mobile ApplicationMobile Web
Supported CountriesGlobal

Frequently Asked Questions

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

Consumers0%
Small Businesses (1-50 employees)10%
Mid-Size Companies (51-500 employees)57%
Enterprises (more than 500 employees)33%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(120)

Attribute Ratings

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Magnolia is used across different business departments (3 Magnolia systems supporting several portal sites). The main business problem being addressed is to split different authoring/editing activities into multiple teams. There is heavy usage of light modules so many separate frontend teams can focus on creating frontend apps on top of Magnolia systems.
  • Easy to start authoring (simplicity during editing pages/ components) as the UX is straightforward for newcomers.
  • Flexibility by proving light modules that helps front-end developers work independently compared to backend/Java modules' developers.
  • The personalization mechanism is easy to use (the variants/traits logic is really simple to familiarize yourself with).
  • The multiple site mechanism is easy to set up (for EE version) even for non-developers.
  • YAML configuration flexibility is easy to change on the fly (for developers).
  • There is a need for out of the box ready & reusable components (customizable components, e.g. banners).
  • Resource (js) loading mechanism (resources can be added at multiple levels: e.g. pages, components, files, etc.) is very hard to manage sometimes in real projects.
  • The drag 'n drop of components in UI author is not supported.
  • Documentation needs a lot of improvement, especially for migration to the newest version (Magnolia 6.2).
  • It would be nice to add integrations with other CMS systems (e.g. Adobe AEM, Hybris, etc.) or other systems in general.
  • I would appreciate more dynamic renditions for images/assets (e.g. now there are only predefined dimensions - thumbnails/medium, etc.).
  • I would appreciate improved functionality for publishing & unpublishing during a specific date & time.
Well suited for Systems with big website content & multiple sites to manage (if set up properly - performance is very good), many different teams/users that are authoring different sites/business areas, and custom content apps for simple data units (and rest entities). Less appropriate for: Systems maintaining more complex data structures (including big data etc.) and integrations with other systems (e.g. commerce) when other CMS products include ready solutions.
Web Content Creation (7)
55.71428571428571%
5.6
WYSIWYG editor
40%
4.0
Code quality / cleanliness
80%
8.0
Admin section
70%
7.0
Page templates
60%
6.0
Mobile optimization / responsive design
70%
7.0
Publishing workflow
70%
7.0
Form generator
N/A
N/A
Web Content Management (5)
26%
2.6
Content taxonomy
N/A
N/A
SEO support
N/A
N/A
Bulk management
60%
6.0
Availability / breadth of extensions
70%
7.0
Community / comment management
N/A
N/A
Platform & Infrastructure (2)
70%
7.0
API
60%
6.0
Internationalization / multi-language
80%
8.0
Security (1)
80%
8.0
Role-based user permissions
80%
8.0
CMS programming language or framework
N/A
N/A
  • It improved page loading time due to caching mechanism for pages with many different components.
  • The integration of different frontend (Angular/ React) apps with Magnolia (as a backend system) made use of the light modules.
  • It provides a custom Magnolia system to authors/publishers using the decoration mechanism (e.g. same app but different configuration per role using decorations).
  • Negative: the flexibility of deploying light modules sometimes is easily propagating errors into the production systems.
The usability of the system is pretty good, especially for editors. There is some lack of documentation, especially for developers for the newer Magnolia system (6.2).
Magnolia's performance in frontends (template rendering) is fine. Caching (EHCACHE3) implementation helps deliver faster pages/components, etc. Performance issues are noticed when having lots of definitions (e.g. components/page templates, etc.). When opening definition apps, it takes a significant amount of time to load all definitions. When Magnolia integrates with other systems, I have not noticed any slowness, but this also depends on any custom implementations (handling responses, etc.).
Used CMS: Hybris CQ5/Adobe CMS AEM
Yes
The release was smooth during deployment. However, lots of issues were found during analysis and real implementation. Sometimes, documentation was lacking for features or migration guidelines from Magnolia 5.7 to 6.2.
Return to navigation