Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
716 reviews
from
External reviews are not included in the AWS star rating for the product.
Hygraph provides the seamless integration
What do you like best about the product?
The headless CMS architecture of Hygraph separates content from presentation, allowing for seamless integration with various front end frameworks which extends the capability. This flexibility enables users to work with their preferred front end technologies while easily connecting to any backend system which helps for the customization and cater the various needs which suits best for my organization. The other best thing is the distribution of content in a modular and customizable manner, empowering content creators to focus on generating high-quality content.
What do you dislike about the product?
There is no speicifc dislikeness of Hygraph.
What problems is the product solving and how is that benefiting you?
It helps a lot for the content fragmentation, Hygraph enables content federation by unifying content from various sources of the connection into a single API endpoint and also eliminates data silos which leads to reduction in the complexity.
Great, user-friendly CMS for all kinds of platforms!
What do you like best about the product?
It's so easy to use. The model and entry user flow is very simple, but also very robust if you're willing to dive deeper into the nitty-gritty. Integrating/implementing it into your platform or website is also very easy if you know what you're doing!
What do you dislike about the product?
It's difficult to find issues with Hygraph. I've mostly just had positive experiences with it thus far.
What problems is the product solving and how is that benefiting you?
Content management for blog posts and unique pages, with language control, an approval process, and versioning.
Easy to set up headless CMS
What do you like best about the product?
Easy to use, comes with a lot of features such as api background and holds your content for you.
What do you dislike about the product?
Some backend doesn't always work, have to sometiems find work arounds.
What problems is the product solving and how is that benefiting you?
It's saving me time setting up a backend database.
Perfect Headless CMS
What do you like best about the product?
Speed and pricing plans, they are offering free plans as starter
What do you dislike about the product?
Probably that pricing starts from 300$ could be smaller package
What problems is the product solving and how is that benefiting you?
Custom CMS for cusom software solutions
Good user experience
What do you like best about the product?
Easy to understand the ui and logic to create content types and components
What do you dislike about the product?
Content type creation and components is mixed with content creation ui.
I'd like more separation on this.
I'd like more separation on this.
What problems is the product solving and how is that benefiting you?
Content management in the easy way
Many good qualities but lacking some, like preview settings to see pages before live.
What do you like best about the product?
Ease of use with the CMS. Ability to quickly grab media.
What do you dislike about the product?
Lack of preview page to see changes before pages go live.
What problems is the product solving and how is that benefiting you?
SEO updates
Wonderful discovery of GraphQL through your platform
What do you like best about the product?
Hygraph is so easy to use that it is not real. Every "problem" we had with hygraph, your platform covered it thoroughly. We left few messages in your Slack community chat and got the answers in half an hour. We are about to embark on a project that uses your platform as their CMS for page views and when I learn new technologies its usualy painful, but with Hygraph, all is good baby... Thanks alot for making this wonderful platform of yours... Best regards from VegaIT Serbia :)
What do you dislike about the product?
This is not dislike in a way but some feedback that may or maynot make sense to you guys. Not long ago we got an offer to maintain an already existing web application that uses Hygraph for CMS. The problem was with signing all FDA papers in order to access the content on Hygraph, with all the birocracy that comes along with it. So my suggestion is that, if it is somehow possible to make a feature to extract just the schema of GraphQL as a file or something, so that someone can just import that schema into their own project and have same template for data entities. Then after tha, development team can just mock as much data as they need. Good for Product Owner good for developers, without any wait time we can jump right into figuring out the entities of the system.
What problems is the product solving and how is that benefiting you?
The biggest problem that Hygraph as a platform solves is that there is no need for whole bunch of frontend features for content management. All the problems that come alongside with forms, modals, validtions,... goes away. You get your nice looking UI, you add stuff if needed, edit it with ease. It saves alot of time, its secure and reliable.
honestly im very satisfied
What do you like best about the product?
the user experience was the best of any other platform
What do you dislike about the product?
the input UX wasn't that good for me so it would be better if you think about that.
What problems is the product solving and how is that benefiting you?
it solve the problem of being struggling with API
Using it for our headless Magento 2 app
What do you like best about the product?
Easy to setup and run with. Works well as a CMS and no major issues.
What do you dislike about the product?
The blog design too is frustratingly limited in control of images, text and spacing. All blog posts, despite our best efforts with the tool set, all look like basic HTML with images that default to very large and small text.
What problems is the product solving and how is that benefiting you?
Hygraph enables our headless Magento 2 environment to function on the front end where there were very few options at the time.
Keeping track of my microblogs has never been easier
What do you like best about the product?
Documentation-wise (especially the API reference) it has improved a lot since docs weren't that clear before. Customer service has also improved a lot too.
What do you dislike about the product?
Usage limits are something to watch out for when working with the API. The UI can also become clunky at times.
What problems is the product solving and how is that benefiting you?
For me it's solving the problem of overbloated websites that other CMS cause (such as wordpress) and also managing multiple microblogs without any downtimes
showing 441 - 450