Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
698 reviews
from
External reviews are not included in the AWS star rating for the product.
A dream to work with GraphCMS
What do you like best about the product?
Having a native GraphQL CMS makes everything much easier to work with. Integrating webhooks and maintaining 10+ locales is seamless fo rus. Developers are much more efficient when building requests, and the product team has granular visibility over every integration step. 10/10 Support as well!
They have constant product updates and periodic feature updates with a very well maintained feedback submission system.
They have constant product updates and periodic feature updates with a very well maintained feedback submission system.
What do you dislike about the product?
It would be nice to have a few more custom roles for each individual contributor we work with, but its possible to circumvent this on the frontend with our own authentication permissions.
Another nice-to-have would be integrations, but from their public roadmap I can see its being actively worked on.
Another nice-to-have would be integrations, but from their public roadmap I can see its being actively worked on.
What problems is the product solving and how is that benefiting you?
We maintain about 10+ locales with the content for each managed in different locations. GraphCMS makes it much easier for us to structure the content needs for each website with granular accuracy. Their documentation is top notch to have a perfect implementation with React making it much faster to implement changes or new projects compared to other alternatives we've used in the past.
Recommendations to others considering the product:
Terrific support team and fantastic product. If they keep up this way there's no real need to switch.
Finally a CMS bridging the dev<>mkt gap!
What do you like best about the product?
We love the crisp UI and the simple implementations. The entire migration of 3 websites and 2 mobile apps took a matter of weeks, and the scalability is brilliant. From all the CMSs we used, GraphCMS had the best internal feedback - frontend is thrilled with GQL and our marketing team loves the editor. And their support is top notch!
What do you dislike about the product?
The interface looks a little dated but incremental updates trickle by. There's a few features missing, however they have an open feature request board that's updated regularly and taken into consideration.
What problems is the product solving and how is that benefiting you?
Centralised all our content for our sites and apps into one hub, which makes it much easier to manage content for all our platforms. Frontend doesn't need to hassle backend for API maintenance, and marketing doesn't need to constantly approach frontend for debugging or deploying updates.
Recommendations to others considering the product:
Its lean and quick to setup, we've had no issues even with enterprise level demands, however be aware that Gcms is still implementing a lot of updates since they're relatively young on the market, however most definitely in the right direction. They're not an AEM at the moment (thankfully) but are still capable of delivering the same capability.
Great User Experience!
What do you like best about the product?
GraphCMS is easy to use and has a clean UI. Schemas are fully customizable and with a great range of options. It helps to save a ton of time and work when creating new content for a website. The generated GraphQL API is exactly what we were needing for handling our content.
What is also really helpful, is having a Draft and Published status for the content. We use Draft for our dev environment and Published for production, the process of updating the status to Publish is a 2 click action which is great to make fast changes.
What is also really helpful, is having a Draft and Published status for the content. We use Draft for our dev environment and Published for production, the process of updating the status to Publish is a 2 click action which is great to make fast changes.
What do you dislike about the product?
The only downside I can find, and it's a personal preference, is that I would rather have the content listed in descending creation date order by default, instead of ascending.
What problems is the product solving and how is that benefiting you?
My company has an entertainment website, with new-age, astrology and lifestyle articles. We save a lot of time with GraphCMS as it allows us to upload content quickly. It's also easy to delegate the creation of new content to a content manager with no technical knowledge since the UI is very friendly.
A perfect GraphQL based backend for even for Mobile
What do you like best about the product?
It has a great UI/UX, and a flexible Schema's design API
What do you dislike about the product?
When dealing with images having to upload assets before being able to link theme, it would be better if we can upload images directly when we link theme
What problems is the product solving and how is that benefiting you?
I am dealing with reach data when working with GraphCMS, structuring and editing data seems really easy, then on the mobile side consuming data using GraphQL have a huge benefit for statically typed models, and minifying the amount of data needed for each backend request.
Recommendations to others considering the product:
It is simple to use, and provide a good GraphQL API well structured for dealing with custom, rich data for both web, and mobile solutions, it has a very handy set of statistics.
Easy to use and powerful for blogging
What do you like best about the product?
Noob friendly guides and nice user interface to get someone set up fast.
What do you dislike about the product?
Web Hooks aren't also free (Joking, its only fair they aren't).
What problems is the product solving and how is that benefiting you?
Easy management of blog content and allows me to query my content using graph queries - thus I benefit in querying only the data I need at once as long as I have linked them.
Recommendations to others considering the product:
Understand why and what you can use headless CMS for first. Then read example doc on making graph queries. You will be pretty much set from there.
GraphCMS is the good tool for your static React Gatsby websites
What do you like best about the product?
- Good Support
- Quick Iterations, features added frequently and they listen to the community
- Great for GraphQL lovers
- Quick Iterations, features added frequently and they listen to the community
- Great for GraphQL lovers
What do you dislike about the product?
- Dashboard can be confusing sometimes (some data seems weird)
What problems is the product solving and how is that benefiting you?
Doesn't need to code a backend if you need to do a static website in React.
Gatsby + GraphCMS works very well.
Gatsby + GraphCMS works very well.
Recommendations to others considering the product:
Use GraphCMS to do static React website with Gatsby
Perfect Headless CMS Solution
What do you like best about the product?
We’re huge advocates for Graph CMS for their clean interface, staging that allows us to release easily when we want, graphQL simplicity, and the flexibility of what it allows.
What do you dislike about the product?
I’d love some more content from them to help achieve things that we might not know are even possible or are thinking about but not necessarily know the path to achieve them.
What problems is the product solving and how is that benefiting you?
App and web content distribution
Recommendations to others considering the product:
This is a great option for a headless CMS where you need a product that is moving fast to be the best in market, if it isn’t already.
Loved by our marketing team, scalable, great for multi-language content
What do you like best about the product?
We like the rich-text visual editor, the easy-to-use localization feature (our content is in 11 languages), GraphCMS’ scalability (several hundred thousand visitors per month) and the ability to write content into the CMS programmatically.
Although our front-end design was ready before we chose GraphCMS, the integration was very fast.
Although our front-end design was ready before we chose GraphCMS, the integration was very fast.
What do you dislike about the product?
GraphCMS is built to handle structured data, so its added value is lower if you are only handling freeform texts.
What problems is the product solving and how is that benefiting you?
My team needed a scalable headless CMS for our homepage, company blog, and all of our periodic content. The set-up was very fast. Our backend developers don’t have to maintain the CMS; our frontend devs don’t need to bother the backend devs if they want to use or modify the GraphQL API.
showing 691 - 698