Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
714 reviews
from
External reviews are not included in the AWS star rating for the product.
A very easy and friendly interface to create and manage content.
What do you like best about the product?
The best thing in GraphCMS compared to others headless CMS i've used, is all the official examples and tutorials on how to use the tool while integrating with other APIs and systems. They also explain everything to you on support if you need any help, a quick support and documentation about how to use the platform is very important in my opinion.
What do you dislike about the product?
Haven't disliked anything about the product yet, and although i'm still learning how to use GraphCMS, seems like everything i'll ever need will be available for me. I'd be glad if there was some more content about how to use GraphCMS alongside with Typescript.
What problems is the product solving and how is that benefiting you?
I've been trying to create an e-commerce for small companies and until now GraphCMS is the easiest way to start with something relevant to my client's needs, a very solid way to manage data.
Great Product For Many Use-cases
What do you like best about the product?
Simple to use and integrates with just about any application you may want to build.
What do you dislike about the product?
Nothing, really... It's a great product, can't really find any dislikes.
What problems is the product solving and how is that benefiting you?
Creates a universal CMS for our many apps to access, and makes like simple for our content teams who need to manage content across multiple apps.
Intuitive interface, versatile modeling options, and great support.
What do you like best about the product?
The content modeling and content authoring experiences are simple to set up and easy to use. The GraphQL API playground makes it easy to test access to the content. We can build content structures, add content, and test the API responses within a matter of minutes.
What do you dislike about the product?
While the components within the content schema expand your modeling possibilities and allow you to quickly use sets of fields, it is currently limited as you are unable to nest components.
What problems is the product solving and how is that benefiting you?
Speed to market for content authors as well as performance for our front-end application, making the user experience that much better. The built-in cache and global content delivery network allow us to leverage GraphCMS for more than a single service.
Modern CMS leveraging the power of GraphQL with great team support!
What do you like best about the product?
Great support and very responsive support and they take up requests quickly and provide solutions and extensions if needed.
Clean GraphQL API gives flexibility to the development team and helps them to work efficiently.
Clean GraphQL API gives flexibility to the development team and helps them to work efficiently.
What do you dislike about the product?
Some features are not available such as tagging, tree views, related entry publishing and still few integrations to popular tools.
What problems is the product solving and how is that benefiting you?
Central store for content that can be consumed by other systems, allows integration of other sources to consolidate them.
Flexibility to model content to ensure the channels have the content they need and are not limited by the CMS.
Flexibility to model content to ensure the channels have the content they need and are not limited by the CMS.
Recommendations to others considering the product:
While not all features are available yet, GraphCMS closing the gaps quickly.
Impressed with flexibility, but lacking in documentation and forums.
What do you like best about the product?
I really enjoy the convenient GraphQL interface. There is very little restriction on what you are able to store and I have experienced very minimal latency with the API. The API playground is also quite useful for visualizing queries.
What do you dislike about the product?
The documentation is useful for day 1 and 2 of usage. More detailed documentation seems to lacking for more complicated queries. There doesn't seem to be a forum managed by GraphCMS to get answers from, nor is GraphCMS pervasive enough to have questions and answers on external sites like StackOverflow.
For complex data, the relationship links between schema get quite nasty as well. Maybe the type system can be improved.
For complex data, the relationship links between schema get quite nasty as well. Maybe the type system can be improved.
What problems is the product solving and how is that benefiting you?
GraphCMS provides an easy non-technical interface for content people to curate and control information. It offloads the maintenance of such a database from the engineering team, opening up time for more important work.
Recommendations to others considering the product:
Think through your schema closely before implementation
work well for our use case, but sometimes I feel a more traditional DB solution is a better option
What do you like best about the product?
the flexibility that graphql gives us, the frontend is also well made
What do you dislike about the product?
a tool like liquibase for a db would be useful, also the merging between branches could be better
What problems is the product solving and how is that benefiting you?
we are using it as a headless cms and also some models are built up by users who are not db admins
A great Headless CMS
What do you like best about the product?
I like its interface, its clean model based on object and its capability to reuse the content across different instances. The API playground is also really useful, especially with pre-filled data
What do you dislike about the product?
I don't really like the initial project page: I find it quite pointless for experienced user — I mean, it makes totally sense to onboard new users, but as I get more familiar with the platform, I'd like more on point information
What problems is the product solving and how is that benefiting you?
GraphCMS is a great headless CMS. It helps me in creating some clean GraphQL query and test them in a zap. Compared to my previous experience with Wordpress headless, this is way ahead
Recommendations to others considering the product:
It's a great Headless CMS!
Simple and easy to use CMS, exactly what we needed.
What do you like best about the product?
Exactly what one might need from a headless CMS.
Easy dev setup. GraphQL API, called from a Next.js + Apollo appliation.
Intuitive and simple CMS administration.
Easy dev setup. GraphQL API, called from a Next.js + Apollo appliation.
Intuitive and simple CMS administration.
What do you dislike about the product?
GraphCMS has its limitations, that it only offers GraphQL API, or you have to define your own schemas before using them, etc. But all of this is a price paid for straightforward simplicity. Just great.
What problems is the product solving and how is that benefiting you?
It is a headless CMS, which allows us to build our own front-end, but not care about the admin/cms side. We want to serve blog and other types of dynamic content on our site, but we want non-tech employees from the marketing and sales teams to be able to change that content. And since we did not want to build our own CMS, this is the perfect solution in the middle.
Leading headless CMS!
What do you like best about the product?
Simplicity and well implemented graphql api. Possibility to integrate external services and well written documentation with good examples.
What do you dislike about the product?
Missing support for inputs like html with syntax highlighting.
What problems is the product solving and how is that benefiting you?
Modern and easy content management which just works without any issues. Fast access and intuitive interface with possibilities to extend it.
It's so good to save info and create specifics schemes
What do you like best about the product?
the way how GraphCMS save the data is based on no relational databases. The interface is very intuitive too. You can click on many buttons and you have the security that you'll not break anything.
What do you dislike about the product?
Maybe the suggestion on the playground, it's a little hard to know all the info. Because sometimes we waste too much time looking for the keywords necessary to make a request.
What problems is the product solving and how is that benefiting you?
We need to work with GraphQL and we are looking for hostings and storage applications because we're using Firebase, but we found this solution as it's interesting.
Recommendations to others considering the product:
Nothing bad to say, it's a great service.
showing 591 - 600