Divi vs. Magnolia

Divi has cornered the market on a simple, straightforward WordPress theme that gives some major integrations and functions! Now that I've worked within it for years, I have a much better understanding of how robust a system it is. It takes some practice to get accustomed to but once you "get" it, it is so fun to use. I've shown so many small business owners how to use Divi and I feel that it is much easier to learn than other themes with functions that are controlled by coding or shortcodes. I could play in Divi all day, and some days I do, depending on which projects I am working on at the time

Incentivized

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

• Front end builder easy to design
• Exportable and importable layouts and templates
• Integration with wordpress and many plugins
• Individual template builder to apply to certain post types
• Add on cloud to store and sync your own designs, code snippets
• Can create your own api licenses for different websites

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

• Some advanced features need to be complemented with other paid plugins (e.g., attachments in contact forms)
• Certain Divi elements cannot be nested within other Divi elements (e.g., including an element within an accordion)
• Customizing the header is powerful, but making the most of it is more challenging than the rest of Divi's options

• 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

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.

Divi is overall a great tool to use - I think I would need to spend a little more time to dig into the tool to provide more long term feedback.

Incentivized

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

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

Divi is a far better-looking and easier-to-learn system than Elements. While Elements has flexible columns and more compatibility with third-party systems (Crockoblock), it has a far steeper learning curve. Divi had a better pricing model and was easier to use to work at speed. We also felt it was far more client-friendly for self-editing.

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)

• It's hard to quantify, but it's allowed me to create the face of my website, which currently receives tens of thousands of visits each month. This is largely thanks to Divi.
• It has allowed me to quickly design my own sales and product pages, without having to rely on third-party platforms.
• Divi's lock-in has made it difficult for me to explore other visual builders that might also be interesting for my website.
• Es difícil de cuantificar, pero me ha permitido crear la cara visible de mi web, que en este momento recibe decenas de miles de visitas cada mes. En gran parte es gracias a Divi.
• Me ha permitido diseñar en poco tiempo mis propias páginas de venta y de producto, sin necesidad de depender de espacios de terceros.
• El lock-in de Divi me ha hecho difícil explorar otros constructores visuales que también podrían ser interesantes para mi web.

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.