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 Configured Commerce
Score 6.8 out of 10
N/A
Optimizely Configured Commerce is a headless SaaS Commerce platform built to deliver outcomes for B2B vendors.
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.
The eCommerce catalog side has a lot of benefits to it and has been much easier to work with and customize than the CMS side. It is this integration and using both for a branded marketing website that has the user journey from browsing and leading into the eCommerce side that has been the bigger challenge, outside of the overall stability of the releases with the bugs we have encountered. I think the solution is well suited if you are mainly a catalog site. We, however, sell machinery and solutions that are not sold via the eCommerce site and we need to showcase them on the website. However, we have a core industrial catalog of consumable products that support the machine and solutions purchases which are very well suited for the eCommerce catalog. It is the CMS/Catalog integration that has caused a need for more customizations to the platform and as a result increased costs to maintain, lowering our overall ROI from the solution. We are also a bit hamstrung by having to rely on our development partner to make changes that our digital agency is better suited to do for us in the CMS. It is requiring extra cost and resources as a result. If more functionality could be surfaced, it would be much better.
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.
Integration Jobs/Connections - Providing a good out-of-the-box solution to hook into ERPs and common endpoints.
Design and Development Partner Network to work with - If you have customizations in mind, the Optimizely partner network will give you the chance to find a suitable partner to meet your needs.
Good layout/flow/settings breakdown - There are a lot of "redundant" settings, but the more management access, the better.
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.
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.
Quite flexible and easy to use for daily marketing user tasks, like updating page listings, promotions, and copy. More in-depth tasks like managing product attributes, rearranging product taxonomy placement, and CMS editing are not user-friendly and require a careful and detailed process to follow.
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
It's a mixed bag. The team has been very nice, but there has been an underlying feeling of condescension because we have complained or "caused trouble" over the inadequacy of the CMS component. Also, support for modifications or UI changes has been terribly slow. Understandably, COVID has made life hard for everyone, but there is an expectation that we complete our work immediately, but their team will "put it in queue" when we have a request or find a bug. Further, we certainly feel that we were sold a list of capabilities that we have not seen come to fruition. Finally, the change of ownership 3 times (Insite -> Epi -> Opti) over our implementation period has been both confusing and disruptive.
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.
I was not very involved with this process. It has been 3 years since we made a decision and I can't even remember the name of the other companies we were considering. I was in a different role then so I was less involved with the eCommerce department. I do remember really liking the people we were working with. That played a huge role in our selection since we would be working with them for years on the site.
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.
Automation of updates and integration with ERP has saved time and provides reliable data for the website in sync with ERP
Integration with external PIM has saved time and provides reliable sync with content data for the website. Changes and improvements have been slow and difficult.
