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.
Hygraph is a good tool in the toolbelt for custom frontends
What do you like best about the product?
I like the simplicity of the admin and the ease to use of the APIs
What do you dislike about the product?
The API can be quite limiting in terms of read/write limits when you run big projects
What problems is the product solving and how is that benefiting you?
It's a great backbone for the content editing process by users
Customer oriented product
What do you like best about the product?
Hygraph is very user friendly and even for the least tech savvy individuals it provides a basis for all users to feel comfortable whilst working on their project. I like how before Saving and publishing, you are asked to confirm the elements you would like to publish, ensuring no mistakes are put into play.
What do you dislike about the product?
One thing that could be worked upon is the fact that it is not super clear of how to re-insert a media that has already been uploaded. The button isn't clear.
What problems is the product solving and how is that benefiting you?
Hygraph makes it very simple for multiple parties, with differing technical abilities, to amend the backend with ease. When needing to recor a tutorial for our client, I was initially worried about how this may be complicated, but I was able to explain everything very easily and knew I wouldn't be overwhelming our client with the instructions since it is very self explanatory.
Hygraph is fantastic for webshops
What do you like best about the product?
The possibility of building a product page with blocks. It's nice to re-use blocks on other pages without te need to rewrite the content.
What do you dislike about the product?
Hygraph isn't an easy tool for blogging. The options are, in comparision to Wordpress, limited.
What problems is the product solving and how is that benefiting you?
It solves issues for putting content on our webshops.
Good technical focus for an cms
What do you like best about the product?
Focus on adaptability and technical solution
What do you dislike about the product?
i see a bit of an entry barrier for newer user
What problems is the product solving and how is that benefiting you?
Account mngmt and edit history
Easy to use
What do you like best about the product?
It's very easy to use. The documentation is very clear an it was super useful when imiplementinng Hygraph in my code.
Hygraph is now used every day, and there's still a lot of features that we will be implementing.
Hygraph is now used every day, and there's still a lot of features that we will be implementing.
What do you dislike about the product?
There's a lot of nesting inn tthe queries. It would be gerat if some key attriutes are moved to the top level of the query.
What problems is the product solving and how is that benefiting you?
It's very easy to change and try different content in the wesite without needing to deploy the site everytime.
Super valuable
What do you like best about the product?
Easy setup, fast, iterating new UIs. Nice demo projects to learn front-end frameworks. Beginniner and expert friendly.
What do you dislike about the product?
I want some more traditional CMS features like a customizable backend tabbed layouts.
What problems is the product solving and how is that benefiting you?
Replacing my own Dev Ops for CMS hosting
HyGraph is the CMS answered our needs
What do you like best about the product?
The most helpful is the part where step by step the process of creating content is customized for the specific need of our application. Variety of content we create, it is not easy to find out what step by step is to be created. With this custom step by step process it has been made feasible/
What do you dislike about the product?
The studio mode is not working yet fully. Not sure why.
What problems is the product solving and how is that benefiting you?
Multiple content organization that is to be reverted mutliple times
Used for a personal portfolio site
What do you like best about the product?
Simple to set up, qraphql out of the box
What do you dislike about the product?
Sometimes interface is not that interactive, that may lead to false-positive events
What problems is the product solving and how is that benefiting you?
I needed a simple way to publish projects to my portfolio
Very intiuative and easy to use once built
What do you like best about the product?
One of the standout features is Hygraph's clean and user-friendly interface, which made it incredibly easy for me, as a relatively new developer/marketer, to create schemas and add content.The ability to customise and connect data has been a game-changer for too projects.
What do you dislike about the product?
Can be quite difficult to wrap your head around the build and integrations and it can seem a little complex at first to make some traction. But once done, is great.
What problems is the product solving and how is that benefiting you?
Website and asset management
All about the new Hygraph Studio
What do you like best about the product?
Spending more quality time on the new Hygraph Studio, I can justly state that the platform is more mature now. The more modern interface is clear and dynamic and even fun to work with schema modeling. The process of arranging the content models through the drag-and-drop builder is now quicker and less prone to errors, notably on multifaceted relationship, components, and enums. Having the integrated GraphQL Playground is a huge advantage - this is how I test the nested queries structure or filter structure before sending them into my frontend (React + Next.js). Among the features that I find most useful, there is a possibility to use Remote Sources. I sewed a third-party API and married it to the CMS-managed content in a trouble-free fashion via the single GraphQL endpoint, and not every headless CMS can so do in this fashion. Regarding performance, the API is quick and delivering assets through their CDN is fast enough when it comes to images and documents.
There is a learning curve in using GraphQL as well notwithstanding, as you should expect among individuals who are not yet familiar with GraphQL. Developers will be okay, but content teams may find the transition difficult especially in interpreting references and content relationships. They have enhanced role-based access, and it would be beneficial to have a more granular control to scale teams. Nevertheless, where a significant number of developers are required, and high-power and flexibility of the CMS, with spectacular support of GraphQL are required, Hygraph makes a darn fine pick, and it appears to grow towards the right direction.
There is a learning curve in using GraphQL as well notwithstanding, as you should expect among individuals who are not yet familiar with GraphQL. Developers will be okay, but content teams may find the transition difficult especially in interpreting references and content relationships. They have enhanced role-based access, and it would be beneficial to have a more granular control to scale teams. Nevertheless, where a significant number of developers are required, and high-power and flexibility of the CMS, with spectacular support of GraphQL are required, Hygraph makes a darn fine pick, and it appears to grow towards the right direction.
What do you dislike about the product?
Hygraph has improved a lot but improvement is always possible. The first is that the learning curve is all too real to those persons not already familiar with GraphQL. Even though there is an in-built playground, beginners can find it difficult to write custom queries, filter the relationships (nests), or process pagination. A graphical query pattern or simulated-life query patterns would help a whole lot. Second, even though the new Studio is easy to use on a developer level, it is still overwhelming to non-technical users such as content editors particularly when dealing with references, unions, or component-based models. Such friction could be reduced by adding contextual tooltips, inline documentation, or a flow to onboard someone.
What problems is the product solving and how is that benefiting you?
It reduces the dependebility for other apps and services . Good help as Assets model is included with each project.
showing 371 - 380