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…
N/A
Optimizely Content Management System
Score 8.7 out of 10
N/A
Optimizely Content Management System (CMS) is used to deliver digital experiences across channels and devices with a marketer-friendly interface, AI-generated insights that drive real-time personalization, and flexible content delivery options—including headless delivery.
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.
Well suited to an organisation who wants a real presence and a superior customer experience when visiting your website. Very modern look and feel and is great for hosting videos and specialist graphics. It is hard to fault the product and it is up there amongst the best in the market
Speed of development - time to delivery from zero to MVP was excellent
Ease of use - the authoring experience is very easy to build and train
PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.
A centralized UI to maintain multiple websites using a common entry point.
Page types and blocks that can be highly customized using .NET code, but at the same time allows checks and validations when being created by Marketing/Content Users.
A very good set of extra libraries/add-ons that allows to expand website functionality in a very short period of time (Content APIs, Personalization, A/B Testing, Social)
The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.
On the technical side, Spire is all built on React Redux, so there's a React framework and then Optimizely built their own framework on top of that React implementation, which is, I'd say customized and non-standard. So learning that as a developer is usually a four to five month learning curve. So that is a con where it's not a standard React redux implementation.
Since I work on the implementation side of things, and do not directly own licensing for Ektron CMS, I have to base this rating off of how I think it will be received or presented to customers looking to start a new site deployment. I try to remain CMS agnostic, though my specialty is with the .NET and Microsoft stack. Because of the experience I have working with Ektron, I tend to be more forgiving with the shortcomings as I am familiar with how to work around them or past them from experience. Being familiar with the community available also helps, as you become familiar with the best approaches to find solutions to your issues. Each product has it's ups and downs and all of them are only going to be as good as the company or development team implementing them can make them. This is EXTREMELY important to remember when choosing a CMS, as it can make or break your expensive investment.
We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
The Opti CMS is pretty easy to use once you get used to it. Setting up the experience editor takes some time and difficult to follow and do in a group setting. We found working one on one or in smaller groups works better
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
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
I attended multiple trainings/tutorials early in the process. The vendor-supplied content about Optimizely was engaging for users/attendees (I often analyze training content, compliance programs, governance plans), which helps our OCM people by having good "word of mouth" about the product long before a rollout ever happens. I actually when the user-focused portion of the Optimizely Academy twice in 2022 to ensure I had a grasp on operability and to be able to support the training and OCM efforts
Ektron is one of the best solution for .Net platform. Over the years have improved the performance issues that the previous versions had. My only complain is right now you can't do Page builder pages if you choose to have a MVC architecture
I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
Optimizely CMS is part of a more composable suite when it comes to DXPs. With that, some other systems like Sitecore Experience Platform are monoliths, which makes the development and maintenance of those products fairly complex (this includes system architecture). In our experience, Optimizely makes it simpler to implement solutions in a rapid manner and "tack on" additional products if needed as organizations grow and are able to leverage that functionality.
Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
The software is affordable with no compromises on capabilities and therefore it is gives us value for money.
