Magnolia vs. Sitecore Digital Experience Platform

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

Having worked with other DXP platforms, I find Sitecore to be the most suitable for enterprise-level clients. The platform is highly flexible - both customizable and extendable - making it adaptable to any customer needs or requirements. The platform focuses on the success of both marketing and technical teams, which I don't see on other platforms.

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

• Customer Profiles - the ability to identify key features on the site and flag those interactions to tie customer visits back to specific persona types.
• Lead Scoring - the ability to establish a funnel for leads and use this funnel to assign a score or qualification within the sales funnel.
• Personalization - the ability to tailor experiences to unique customer segments based on their needs, identifiying and optimizing the experience in real-time.

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

• Sitecore is complicated. Software developers need (costly) training to get the most value out of it and business users do not find it intuitive to use. Concepts like the content tree can be difficult for the business users to grasp.
• Despite everything being possible in Sitecore, virtually nothing comes out of the box - you need to develop every component and do so within a defined process and framework, which can be a fairly big development overhead.

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.

Sitecore has proven that it can deliver on its promise of a robust, reliable enterprise CMS solution with plenty of features. Also, they keep updating it with more and better features. Now that we are highly trained on it we have started on getting the most out of it and we plan to keep doing more of that in the future.

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

Once you learn how to use the platform and can put a solid strategy in place to manage it long-term, it becomes a lot easier to use. The tricky part is working with resources who are familiar with the platform to navigate some of the common implementation and configuration pitfalls. Although Sitecore has worked very hard to overcome some of these from their earlier product versions by creating wizards and improving their support documentation, at the end of the day it is still a very complex and powerful system that needs to be implemented carefully in order to foster the best possible user experience for authors. So it could be rated very usable or not usable at all based on how much planning took place and the quality of the implementation.

Incentivized

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

1. Customized software development & maintenance. 2. Technology Consulting - Consulting-based services for technology solutions data engineering or cloud solutions. 3. Used for tapping into multiple data sources such as CRM and marketing automation systems and, creating automated data extracts with a high-end visual representation of data. 4. Implemented for scheduling an existing report to automatically refresh and be delivered to specific users at a specific regular interval.

Incentivized

Sitecore captures and remembers every single interaction your customers and prospects have in any part of the system, allowing you to build comprehensive, ever-learning profiles of each individual. From email marketing, to social media, to online shopping, Sitecore remembers where each interaction left off so you can automatically continue the conversation. Sitecore helps you manage your content for each and every experience your customers enjoy. Customize what content you want and the system will take care of how it's displayed.

We implemented Sitecore on an Agile project team, which worked very well. We worked closely with the stakeholders for each feature and all features and user stories were prioritized outside of the development team. Anyone trying to implement a website of this magnitude should definitely attempt to do so in as much an Agile fashion as possible.

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)

Adobe Marketo Engage is a fantastic product for managing campaigns and audience segmentations syncing with Adobe Audience Manager. It also has OOTB connectivity to very popular CRM platforms. Adobe Analytics and Adobe Target are pretty similar to Sitecore CDP/Personalize. Any custom/extension implementation required in the Adobe space has the same complexity as Sitecore.

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.

• Headless capabilities have enabled us to use our favorite frontend framework for rapid development and faster feature rollouts.
• Our team's productivity have improved significantly and we have no hassle to deploy new features.
• We are able to extend the feature set as per our own needs which gives us great flexibility and competitive advantage.

Incentivized