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.
Read full review It is well suited for heavy-duty A/B testing where management would like to see and quantitatively determine the effect of a change. It is not so efficient to try for a single page simple form, except when the form is part of a larger workflow. The security model is not very well understood, including RBAC and protection against injection attacks.
Read full review Pros 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. Read full review Provides quicker release cycle for the way the product cards should be displayed. Provides feedback for new product introduction and how it'll be perceived. Allows rapid blackout from user experience changes that alters traffic flow. Read full review Cons 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. Read full review Can use better interface for managing test, including scheduling and notification. Feels too heavy for simple projects, though this isn't a factor once past the PoC stage. Notification on various aspects can be made more powerful and granular if such a need arise. Read full review Likelihood to Renew We have invested a lot of time and energy into tailoring a solution that works for the company.
We think the new features in v6.2 will help us get to the next level
We also don't have the resources to rebuild a website platform from scratch even if we wanted to
Read full review Usability 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.
Read full review Performance 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.
Read full review Support Rating 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
Read full review Alternatives Considered 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.
Read full review There is a big difference between the two:
Google Optimize uses Bayesian analysis while Optimizely uses Frequenting. There is a risk of counting multiple visits.
Google Optimize data isn't available instantly (if I remember correctly). Optimizely's analyses dashboard is a lot richer and offers a better experience, though it may get intimidating.
Read full review Return on Investment 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. The templates makes the whole process easy Read full review Almost immediate payoff in terms of the benefit. Easy to justify the TTM benefits to upper management. Still somewhat hard to justify ROI, though this is not my expertise. Read full review ScreenShots Optimizely One Screenshots