Divi vs. Netlify CMS

Divi is great if you build multiple websites for clients; however, I'm not sure it is cost-effective if you only make a single site.

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

• It has a very easy-to-use and extremely complete block editor.
• It offers many templates that you can use as a base for your website.
• Customer service has been fast and effective whenever I have needed it.
• Tiene un editor de bloques muy sencillo de usar y extremadamente completo.
• Ofrece muchas plantillas que puedes utilizar como base para tu web.
• La atención al cliente ha sido rápida y efectiva siempre que la he necesitado

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

• The load time of the builder could be faster. On some websites it takes a long time to load, and may crash the page. (I believe they've said they're working on this stability issue.)
• Warnings on updates if they're difficult for some sites to run. I have one website that has crashed more than once from Divi's theme updates. I always back it up before the update so I restore the site, but this is still a bit of an inconvenience.
• Integrated (or more clearly marked) tutorials within the builder. I migrate site maintenance and ownership to clients after the site is complete and some could use refreshers within the builder on what happens where i.e. the difference between a section, row, module.

Incentivized

• 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

I find Elementor very clunky and find Divi much more intuitive.

Also we purchased a lifetime license for Divi and can use it on unlimited websites, while Elementor there is a yearly subscription per site

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

• Higher conversion rate
• Theres no needed more tools
• Ive got rid of a CTA tool since with Divi i can make them. Is not that easy, but is functional

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