Divi vs. Netlify CMS

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

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

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

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

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

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

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

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

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

• 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

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized