Divi vs. Hygraph

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

I would recommend GraphCMS to anyone who is also using Gatsby to build their website. If not, I would recommend them to consider GraphCMS but also consider other options. GraphCMS is a tool in which you are responsible to make the most out of it, but sometimes this requires more time and knowledge than a normal engineer may be able to handle. But with more time and attention, the reward of off-lifting content creation from the developers is a huge time saver in the long run.

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

• GraphCMS is easy to work with from the "non-engineer" side of things.
• GraphCMS is very flexible on what data models we can create and how those models are formed.
• GraphCMS uses Graph API, which is easy to write (compared to older API patterns).

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

• GraphCMS is very expensive at the enterprise level.
• GraphCMS requires deep knowledge of the system and requires lots of time to be efficient with it (especially around creating specific data patterns/relationships).
• Multiple times a day, the system will give us errors when attempting to save something but the errors are unclear as to what went wrong (can be irritating).

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 picked GraphCMS since it used Graph API and easily integrated it into our Gatsby website. It was also cheap (free) and easy to test out the product, making it easier to prove to our company we should pay for the product in the long run. Lastly, it seems to have a bunch of support from other developers which makes us confident will be around for a while (and we won't need to replace it anytime soon). Note: I also looked at Directus and DatoCMS but these were not options within TrustRadius

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

• Better use of time for our engineers in the long run.
• More control of content for people outside of the engineer team.
• Allows people to edit the content on their own, so they don't need to wait until a developer is available to add something to the website.

Incentivized