Contentful vs. Divi

Contentful is well suited for folks who want a simple, clean, easy-to-use interface for a JAVASCRIPT website. If you do not want a javascript website you should look [elsewhere].

Incentivized

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

• Clean, modern interface (not clunky and outdated, like WordPress)
• High degree of flexibility (I can structure data any way my clients need)
• Enables headless frontend (i.e. I can build any frontend I want without having to change my CMS)

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

• The new Contentful "branches" feature looked promising (it appears to mirror a git-like repository) but it requires the CLI, which isn't necessarily practical for teams that aren't current CLI users. It would be nice if the management of this feature were available via the UI (without that it causes more confusion than anything).
• The Contentful data modeling method makes for a bit of an awkward SDK developer experience in some strongly typed languages like Java. Most things that you might need can be accomplished, but it feels like the experience could be smoother.
• It would be nice if there were a way to migrate data between spaces (e.g. from your staging space to production).

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

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

Easy to use and much more organized as a single platform versus multi. The layout is clean and easy to read and we don’t have to worry about certain users safe guarding data or content then losing it when they leave the company. It’s a one stop shop for imagery

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

• There was no negative impact as such.
• Positive impact is increase in sales.
• More work is delivered due to reusability and other features within a time and less manual effort.

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