CommonSpot vs. Hygraph

Commonspot is well suited for web content management to be conducted by individuals with low-level web skills.

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

• I think CommonSpot's greatest strength is its ease of use. It's relatively intuitive in it's usage, so it therefore makes it easy to train new people to use it.
• Within my usage of it, our options were limited, which again added to it's ease of use.

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

• Commonspot needs to improve on its authoring feature. It is impossible to author on more than one page at a time . (One must always click on "View work on all changes") before switching between pages otherwise, the changes will not be saved.
• CommonSpot does not support sharing the definition of any custom element or any template layouts. Therefore, one must recreate these in each site.
• In Commonspot, a user who has to manage content in multiple sites will have to log in to each site to see and act on any actions.

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

I had no previous background in content management, and found it very easy to use. If I could figure it out, I am pretty certain that just about anyone else could as well.

Incentivized

Commonspot works in tandem with Zendesk very well to accomplish tasks an an efficient manner.

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

• I was working in a religious institution and based upon our usage and audience, there was no ROI to speak of. Our usage was more for providing information than having any type of interaction. In that instance, it worked very well.

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