Magnolia vs. Optimizely Content Management System

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.

Incentivized

Very much if a business is doing a rebrand, for example, or a digital transformation, the DXP product is super competitive. The managed services that provided around the infrastructure and all of the moving parts really, really works well. It just makes life as a developer very easy when ultimately you just have to do the code and deploy it out and don't worry about the environment infrastructure. I think it's really, really well and fits in really well with that. Areas where it's not so great in my experience, I would say, well, I've already mentioned kind of the CMS to SaaS product, but also just in general it feels like we're going through a bit of a transition period with the documentation at the moment. So when new features are rolled out or the product catalog expands, the documentation isn't always the best or streamlined. That can make life as a developer a little bit work at the times.

Incentivized

• Use of YAML to define content models with code.
• Versatility of defining actions for custom handlers.
• Reloading classes when code is modified in a local dev environment is nice. While it doesn't seem to work when changes extend beyond the method body (i.e., adding methods), it remediates the pain of long startup times.

Incentivized

• Folder structure - I was on Magento 1.x & 2.x for 10 years, which had no folder structure for blocks or images - it was very difficult to find things. We couldn't keep anything straight without it.
• The fact that it knows what block or image is being used and links to where it's being used is pure gold. It prevents deletion of needed elements.
• I like that I can drag a block or image somewhere new and it doesn't break anything.
• Our search of blocks and images is now working, that's very helpful.

Incentivized

• As a developer the learning curve is long, you can start developing relatively quickly but getting to know the platform in depth takes time.
• Having a history of modifications not only at the page level but also at the Content Apps level would be very useful.

Incentivized

• promo types, several have been released that do not work as they are advertised/labeled which has caused us to make custom promos for just about all of them where we've actually fixed the functionality. The OOB types are completely unreliable
• promo exclusions/sorting -- this is very buggy, and some of this would normally be "out of the box" like no two order discounts should ever be able to stack. This gets incredibly difficult to manage when you have 75 active promos at a time.
• asset management - replacement files with same name aren't recognized even when the first version is deleted, this creates a mess in asset folders - nothing can be successfully deleted from epi asset library
• html automatic edits -- issues when typing in either content page links or asset links, epi always adds random characters to the end (?"Epieditmode=false,6789" for example, which doesn't break content, but does make it more difficult for the team to use non-epi html tools to build or edit
• auto dimensions on images -- when adding an image in the html, you have the address exactly, but any other way causes the editor to put width and height dims on the code, making the image warp in mobile, this is adding steps to undo the automatic edits, they are completely unhelpful
• blogs - we are running a blog in Opti that is compeltely manual, every "related article" and every "articles about x topic" block is hard coded, there is nothing dynamic in the content library which is frustrating, and creates a huge time suck for articles across the site, every time there is a new one, that's 10+ manual page updates

Incentivized

Magnolia is an innovative CMS, for example it is possible to use the ipad to manage the contents. Magnolia’s team works hard to improve the product; the community is small but active and the support for the enterprise version is good. Magnolia’s team asks the users what they think and what they need, and the new functionalities planned for Magnolia 5.3 are very exciting for example the content personalization.

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.

There are a ton of small things that could make this CMS great Off the top of my head... 1) Better navigation between a component and its corresponding node in the jcr ( devs often have to flip between a page and a spot in the jcr even though there could be a button to take you from a page/component in the pages app to its location in the JCR) 2) Why does a content editor need to open the page to edit the page properties? They could just as easily edit the dialog from the tree view if they have many pages to touch, and it would save them time by not having to render the page.

Incentivized

From our editors perspective they find the CMS system easy and to clear to use. Our developers find it very easy to design on and appreciate the level of service support available. It's also always evolving and getting better every year. We find this investment reassuring and encourages us to try keep pace and see how we can continue to push the envelope and continue to improve all aspect of our websites and online touch points.

Incentivized

Unplanned outages or errors are fairly rare in our instance. And when there are issues, they're usually fixed fairly quickly

It's a lean and performant platform. You don't need to put reverse proxy servers in front of it to speed it up (although that does make it go even quicker) as there are various layers of caching built in to the application. While it's a little cryptic, the internal caching system is actually quite configurable and can be tuned to the right sort of content.

Often what tends to surprise many an IT manager is that you can run it on relatively modest hardware. We've often been met with "are you sure ?" but the reality is that it doesn't need a whole lot of horsepower.

Incentivized

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

Incentivized

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 was not fully involved.

Incentivized

Magnolia DXP offers similar or more capability compared to the other platform, while much easier to implement. For example, Adobe Experience Manager tend to be more monolithic in nature, heavier footprint compared to Magnolia. Hence when implementing a DXP, it is much faster to build using Magnolia, at a much lower TCO. The other platform like Kontent.ai and Strapi are pure headless platform and offer lesser features. What really make Magnolia different is the APAC team, who are all out to support their client in the implementation, ensuring their client maximize their platform and the project implementation is successful. This is some thing that is not experienced when using other platform(s)

Optimizely Content Management System takes the best bit of previous platforms and simplifies them without removing the more advanced features but not making the necessary to get things going. allowing for any user to jump in and start working is a massive help but empowering power users to take advantage of all its features.

Incentivized

• We have placed web content management in the hands of the organisation than retained it within the technology team.
• We were able to quickly move to MVP and release and we are now focussed on moving the platform forward at some pace whilst not being burdened with BAU work inside the technology team as so much as self-service to trained organisational users
• The use of the SAAS/PASS has inbuilt business resiliency as specialist work and aspects such as underlying security is done by Magnolia and we are able to focus internal effort on building out the platform.

• Flexibility with design that allows us to work towards our mission of 'Tennis Opened Up'
• Speed of deploying content, meaning users can really on us for the most up-to-date content on tennis in Britain
• Ability to have different logged-in areas for different user groups, allowing us to create more bespoke and personalised experiences

Incentivized