Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
701 reviews
from
External reviews are not included in the AWS star rating for the product.
Love the API Playground
What do you like best about the product?
The API playground is so helpful for testing the fetch requests and seeing how the data is rendered.
What do you dislike about the product?
For a beginner to headless CMS the learning curve was quite steep but there are tonnes of educational material out there and once you get the hang of it, it's super simple
What problems is the product solving and how is that benefiting you?
It's making scaling my amount of content much easier so I can focus on styling and other passion projects
The only headless CMS you will ever need for NextJS
What do you like best about the product?
Well, it is a very revealing feeling to start working with GraphCMS (Hygraph) after trying other similar solutions.
When you are a developer working with bleeding-edge technologies and frameworks such as React and NextJS you need an exceptional solution for content API that seamlessly integrates with your current technology and I believe that GraphCMS has done an amazing job by providing such a solution whether you are starting a simple marketing website or trying to build the more complex solution.
The learning curve of GraphCMS is simply amazing as they provide real project examples, their documentation is clear and the interface is intuitive.
It is a GraphQL CMS and it is behind the scene making your queries easy to structure and adapt to your needs.
Overall very pleasant experience.
When you are a developer working with bleeding-edge technologies and frameworks such as React and NextJS you need an exceptional solution for content API that seamlessly integrates with your current technology and I believe that GraphCMS has done an amazing job by providing such a solution whether you are starting a simple marketing website or trying to build the more complex solution.
The learning curve of GraphCMS is simply amazing as they provide real project examples, their documentation is clear and the interface is intuitive.
It is a GraphQL CMS and it is behind the scene making your queries easy to structure and adapt to your needs.
Overall very pleasant experience.
What do you dislike about the product?
Rich text field inside component does not support embedded feature. It would be amazing to add it there.
Other than that we are still discovering all amazing features.
Other than that we are still discovering all amazing features.
What problems is the product solving and how is that benefiting you?
Seamless integration with NextJS and many other frameworks.
GraphQL-based means you can easily construct simple and complex queries in the question of minutes. They provide a great playground for that even if you are not familiar with GraphQL.
Unified content API. Connect your website, your app, or any other platform.
GraphQL-based means you can easily construct simple and complex queries in the question of minutes. They provide a great playground for that even if you are not familiar with GraphQL.
Unified content API. Connect your website, your app, or any other platform.
Recommendations to others considering the product:
Just set up a project that adapts to your current technology and use their examples to start with.
Great Developer and Content Manager experience
What do you like best about the product?
The api-driven headless approach was one key aspect driving our decision to run this pilot with GraphCMS. From the Agency point of view, we required a scalable on-demand solution that is able to cover our technical requirements without the need for further infrastructure - reducing the cost of ownership for system setup and ops resources.
For our developers it GraphCMS supports easy integration with most modern tech stacks (ReactJS in our case) - everything is well documented.
The OOTB support for GraphQL allows our Frontend developers to concentrate on building features without involving backend developers for API adjustments. They can swiftly built and test queries inside GraphCMS intuitive UI which allows us to flexibly shape the content models and test the outcome almost immediately in the frontend.
For our developers it GraphCMS supports easy integration with most modern tech stacks (ReactJS in our case) - everything is well documented.
The OOTB support for GraphQL allows our Frontend developers to concentrate on building features without involving backend developers for API adjustments. They can swiftly built and test queries inside GraphCMS intuitive UI which allows us to flexibly shape the content models and test the outcome almost immediately in the frontend.
What do you dislike about the product?
There is nothing we disliked so far. Overall we also liked the easy-to-use interface for content managers, the detailed developer resources and documentation for various tech stacks as well as having a Customer Success Manger from GraphCMS on our side offering quick support when needed.
What problems is the product solving and how is that benefiting you?
For our client - being a global organisation - it is always challenging to provide local solutions for individual subsidiaries - especially of the requirements are so specialised that we cannot make use of the existing components offered in their Enterprise CMS.
Usually local solutions would be built statically to be packaged and uploaded into AEM. Of course this comes with some drawbacks - in particular for maintenance and continuous content updates
The current technical static setup and code-base for our project was too rigid for easy maintenance and regular updates. We needed a scalable and proven solution to deliver content in a flexible, design-agnostic way into our new React based SPA (Single Page Application).
It should be easy to onboard new content managers and publishers to enable them for fast content updates while allowing the developers to work on critical features and enhancements.
Usually local solutions would be built statically to be packaged and uploaded into AEM. Of course this comes with some drawbacks - in particular for maintenance and continuous content updates
The current technical static setup and code-base for our project was too rigid for easy maintenance and regular updates. We needed a scalable and proven solution to deliver content in a flexible, design-agnostic way into our new React based SPA (Single Page Application).
It should be easy to onboard new content managers and publishers to enable them for fast content updates while allowing the developers to work on critical features and enhancements.
Amazing CMS for blog posts designing
What do you like best about the product?
I am using graphcms's blog post creation for our site, where the I am writing posts with graphcms Editor flawlessly. The data is pulled from cms very fast. love it.
What do you dislike about the product?
Nothing as of now. Graphcms has provided me the best experience ever.
What problems is the product solving and how is that benefiting you?
It is utilized for dynamic Content management where you generate content on simple Text based editor and you will fire its APIs to load that dynamic data to your website.
Given graphcms good design, my difficulty of creating blog posts has reduced to higher extent.
Given graphcms good design, my difficulty of creating blog posts has reduced to higher extent.
Very easy to use and set up
What do you like best about the product?
It comes with speed and GraphQL integration, and it's very lightweight. It doesn't come packed with features I won't use; I can set up my own schema and have only what I need available. If I need to add new fields later, I don't have to break my entire website to do it. Overall I'm very happy with GraphCMS, as it provides exactly what I need.
What do you dislike about the product?
EDIT: I just noticed that I can save my column configuration as a custom view! Zero complaints now. :) [This is a very tiny nitpick, but when I view content I've created I have to customize the column view each time as it doesn't seem to get saved. Sometimes I'm working in split-screen view and I'd like to be able to see the content title without having to scroll right. I feel like the title should be further, if not furthest to the left anyway.]
What problems is the product solving and how is that benefiting you?
I have an easy and simple way to store all my project information for my personal portfolio, and it has been a joy to work with.
Love the UI in the dashboard and the super easy API playground!
What do you like best about the product?
The way models are built/handled and having the ability to reference other models, making it super easy to interlink content/models together.
What do you dislike about the product?
I'm a sucker for SEO, so not having the ability to easily add an image ALT tag when uploading a to the assets, is one downside.
What problems is the product solving and how is that benefiting you?
having the ability to create complex content for my static/server render projects.
Excellent response rate
What do you like best about the product?
Easily navigatable and quick to learn, especially for new users.
What do you dislike about the product?
Grammarly extension doesn't apply to the rich text within data models. I would like to be able to proofread my text.
What problems is the product solving and how is that benefiting you?
Its simplified development is great for users that consume it for the first time, including new content managers joining my team.
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.
showing 571 - 580