Magnolia Reviews and Ratings

Use Cases and Deployment Scope

We are using Magnolia as the platform to centralized all our content and content production in one place. Leveraging on Magnolia's open architecture, we are able to quickly connect to our e-commerce platform to generate reusable front-end components and churn out programmatic SEO pages to scale up our SEO keywords. This allows us to scale our digital footprint without corresponding increase in manpower, while achieving our business objectives.

In addition, because of Magnolia's open architecture, we were able to easily connect to the GenAI services of our choice. This help us leverage on Generative AI to scale up our content production and serve as a "co-pilot" for content author.

Magnolia's connectors to CDP allow the organization to connect to our CDP and deliver personalized content across multiple "owned" website and apps.

Likelihood to Recommend

Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities.

One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels.

Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.

Use Cases and Deployment Scope

Our digital platform consists of different parts: SAP commerce for products and their details, Magnolia DX CMS as the main part to add content and some microservices. Magnolia fits perfectly in our system architecture and enables us to invent all necessary organism our editors need. It is easily possible to connect the CMS to other services via interfaces in order to establish communication in all directions. Our editors have to add a huge amount of marketing pages (more then 10000) and also further information to products to the websites. Therefore we need a powerful CMS that fits our requirements.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

Magnolia is our front end CMS serving the content for our B2B website serving 24 countries and 18 different languages. The Magnolia CMS allows our content author to verify, approve , test and publish contents to public instances serving the website contents. It serves both CMS content pages and eCommerce related pages.

Likelihood to Recommend

Magnolia is well suited for both B2B and B2C enterprise sites covering multiple geographies and languages. The platform has evolved over the period of time and offers extensive customization options. The inbuilt applications e.g. pages app etc are a very good starting points. With so many oob components and options to create or customize existing is a good offering from CMS point of view. Magnolia might not be suitable for smaller sized website where you just need few static/dynamic pages with limited capabilities.

Use Cases and Deployment Scope

Good Things Foundation delivers the National Digital Inclusion Network - a set of hubs and services that support people excluded from the digital world. We needed a modern web platform to build our corporate web site and to build a "members area" for members of the Good Things Network. This needed to have all the essential capabilities of a web site plus a signup/login area for content supporting our network. We were also after a single unified platform, a PAAS/SAAS solution, migrating from legacy inhouse built technology.

Likelihood to Recommend

I have little to say on where it is not appropriate - I've used other high end CMS systems and this is by far the best. There seems to be a focus on the CMS market for headless CMS with a front end delivery framework and that is really only appropriate when using significant multi-channel sites. For a small charity as we are, the ability to have an integrated CMS and delivery front end was excellent. I am sure Magnolia would also perform well as headless, so supporting both is crucial.

The weakness I pointed out means that if there are authentication and other integrations needed, more complex development is also needed. I suspect a little bit of alleviation on that would resolve it. Overall its excellent for many use cases for low to high end.

The PAAS/SAAS is not also excellent if not always within the reach of smaller organisations but Magnolia proved proportionate in their pricing model, recognising who we were, which definitely helped.

Use Cases and Deployment Scope

Magnolia is the DXP that we use to manage our 4 websites. Magnolia allows us to update content quickly, manage our campaigns, an offers incredible flexibility from a development perspective. We are able frequently complete and release weekly sprints. We are exploring Magnolia's connection to AI along with personalisation to be able to provide an improved user experience to our guests.

Likelihood to Recommend

Magnolia is extremely well suited to our situation, it provides us with everything we require and if there are features that we would like they are always more than happy to work with us to implement them. Magnolia's cockpit is good as a base but we would recommend exporting data to an external solution for more advise detail into logs, etc.

Use Cases and Deployment Scope

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 our customers.

Magnolia gives us the ability to not only create variations of pages for different users, but also a easy to use UI for our editiors to build pages quickly and deploy to production with no real time delay.

Likelihood to Recommend

We use magnolia to be able to provide a different journey to our users depending on authentication status or persona so we can better target and convert users. Magnolia makes this very easy and is a key factor to us using with the business, also being a headless CMS system allows us to deploy in a variety of ways across a range of platforms.

Use Cases and Deployment Scope

<div>We mostly use and recommend Magnolia for enterprise clients who want a lean, easy to use platform for managing their content (not just on the web). However we do also use it internally for our own website as well.</div><div>

</div><div>It's not the only solution our clients use as everyone has different requirements. Why do we use it and recommend it to others when we do see a fit ? Quite simply, it's a well engineered product which has always been ultra reliable whenever we've deployed it to the dozens of clients who we've worked with it on. We don't like implementing solutions that we have to constantly prod and patch to keep working, and for us Magnolia saves us time, money and credibility. Our clients are always happy to use it because it is simple to use and takes minimal training.

</div>

Likelihood to Recommend

<div>Magnolia is very well suited to scenarios where there are multiple end points for content eg. apps, remote devices, websites etc. and with multiple users. Magnolia is very good at working with different "shapes" of content so it's not necessarily all about HTML content for the web which tends to be the default for a number of other products of this nature. This means that it's more logical for people to work with structured data and easier for the applications to sort and manage that content when they receive it.</div><div>This works really well when you have multiple team members (often in multiple locations). We've had clients who've had people in twelve European locations with sixteen languages and they can share skills and resources between them but still manage their own content.</div><div>

</div><div>Magnolia is less appropriate for SMEs who have fewer digital assets and content. It's not to say that it can't be done but it's more that the budget would not necessarily fit.

</div>

Use Cases and Deployment Scope

We use Magnolia as a content management system for our public website. We also have several headless implementations and we are serving content to other apps.

Likelihood to Recommend

Magnolia is a versatile and robust enterprise grade Content Management. It is not as well suited for regular users or small companies as it requires rather a complex setup. The customer support is providing quick guidance on most of the areas, but you will still need a pretty big team to manage it.

Use Cases and Deployment Scope

I train developers how to use, build and customize every nook and cranny of Magnolia.

Likelihood to Recommend

A colleague here being another business. Magnolia is on its way to being a 'good' product but the 6.2 implementation simply isn't there yet (6.2.26 as of this writing). The admincentral UI could use a complete overhaul to be better streamlined for devs and content editors (the two who actually use it).

Use Cases and Deployment Scope

We use this product to implement CMS solutions for the clients our organization contracts with. Clients may be looking to move away from platforms such as Wordpress to a solution that is more customizable and can be integrated with external systems.

Likelihood to Recommend

It's well suited when there are requirements and handling for content after it's been authored, and highly specific workflows. I would not recommend Magnolia to anyone who wants something that "just works."