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.
Really excellent balance between Developer Friendly and Non developer Friendly (Content Creators)
What do you like best about the product?
I like the interface, support, docs and features like UI extension
What do you dislike about the product?
I wish I could have a third environment without the next major cost increase
What problems is the product solving and how is that benefiting you?
Data closer to the UI and formed in a way that is best for the UI
Recommendations to others considering the product:
The perfect balance between developer and content creator features. Developers are not limited in what they can create. They can focus on the more interesting bits, as opposed to creating forms, roles, servers, etc.
Developer Friendly Headless CMS and BAAS Solution with great support
What do you like best about the product?
The support was ultra quick and amazingly helpful.
GraphCMS goes beyond just providing a headless CMS into BAAS territoy
GraphCMS goes beyond just providing a headless CMS into BAAS territoy
What do you dislike about the product?
The management SDK could use some better error handling and docs
What problems is the product solving and how is that benefiting you?
Using it more like a BAAS (Backend as a Service) solution
Powerful tool that needs some warm-up time
What do you like best about the product?
GraphCMS is a very flexible tool. From simple i18n to full-blown website organization, it's all possible. We use for two cases: first, we use GraphCMS as a localization tool for our platform. So all text that is displayed within the platform is identified by a unique key. In Graph we put a value for each language available for each key. That way, it is straightforward to change translations and text in general. The second use case is our landing page. We have several different content blocks available, e.g., news article, video+text, picture+text, etc. In Graph it is pretty simple to add, remove or edit these building blocks and also to change the content of each block, e.g., texts or pictures. The actual visual interpretation is done in the code.
What do you dislike about the product?
You need to get used to the way of building stuff with GraphCMS. As the code makes the actual decision on how content looks in a given environment, it makes it harder to imagine the final result. However, after some time, you get used to it.
Unfortunately, we have performance issues from time to time, where loading of localized content takes some time. Also, it would be great to publish entire sets of building blocks. For example we have a picture+text block which has an own component nested for uploading and configuring the picture. If you just publish the entire building block, it doesn't publish the picture automatically.
Unfortunately, we have performance issues from time to time, where loading of localized content takes some time. Also, it would be great to publish entire sets of building blocks. For example we have a picture+text block which has an own component nested for uploading and configuring the picture. If you just publish the entire building block, it doesn't publish the picture automatically.
What problems is the product solving and how is that benefiting you?
1) localization on our platform
2) Entire content management for our landing page
-> both is pretty simple as soon as you got used to the way of working with an headless CMS
2) Entire content management for our landing page
-> both is pretty simple as soon as you got used to the way of working with an headless CMS
Great headless CMS. Fast and easy to deploy.
What do you like best about the product?
Smart product. Incredibly easy to use for devs and content managers. Lightning-fast content calls.
What do you dislike about the product?
Per-project price point is too steep for many of my smaller clients, and that will take money out of my pocket as a digital agency.
What problems is the product solving and how is that benefiting you?
Ability to build more secure, faster custom websites and applications for smaller projects.
GraphCMS is great, but the pricing is very steep
What do you like best about the product?
GraphQL (duh), union relations, the whole data modelling, etc.
What do you dislike about the product?
Every model using in a union counts towards an item in the model system. I might have misunderstood the functionality what you guys had envisioned with the functionality. We want to give flexibility to create a page and wanted to keep it as flat as possible. Create a new model, create a new component and assign it to a content union relation field and the customer is good to go to create something beautiful.
With the 'recen't addition to the strict content models we're very limited in what we're able to offer and we have to resort to other solution inside our models.
With the 'recen't addition to the strict content models we're very limited in what we're able to offer and we have to resort to other solution inside our models.
What problems is the product solving and how is that benefiting you?
The content to component creation pipeline. GraphQL is directly used in our app with GraphQL codegen, this creates assurance that the application works as expected.
Amazing tech support saves the day!
What do you like best about the product?
Tech support is excellent. I encountered bugs using the software at first, and they fixed it quickly while keeping me in the loop about the progress every step of the way.
What do you dislike about the product?
It's not the most friendly for non-technical.
What problems is the product solving and how is that benefiting you?
We use GraphCMS at Mage to host the backend for our blogs. It's working fine so far, and in the future, we envision ourselves upgrading our plan as the company scales.
Great services
What do you like best about the product?
Better content management. Thank you!!!!
What do you dislike about the product?
Not any particular! Though I think it can be better.
What problems is the product solving and how is that benefiting you?
Better content management with my Store and my team members
...
...
Very useful and configurable
What do you like best about the product?
The best thing is flexibility. It's easy to add new fields, content types, etc. We've been using it for some time now for several customer sites; all implemented using gatsby.
We've been using the free version as all the content is downloaded and processed in the Gatsby build. It would be great if there was a static site version that was something like $10 per month just so we could give something back to GraphCMS for being so useful!
We've been using the free version as all the content is downloaded and processed in the Gatsby build. It would be great if there was a static site version that was something like $10 per month just so we could give something back to GraphCMS for being so useful!
What do you dislike about the product?
The main thing is you can't easily change one object into another. This means we have ended up creating a generic content block that has different content types. To change how it looks, just change the content type and handle that in the code. Whilst this approach works, it can confuse some people.
There are some other tiny annoyances, such as you can't use a dropdown value as a field for the preview page, so having a 'page type' drop down which is used to generate the url means the preview page doesn't always work. It also took a while to get the hang of locales, but we've got that working now. When building a new site, the ability to publish all content would be useful. It would also be great to be able to dump out all the data. You can do all of this using the API, but it would be nice to have it build in.
There are some other tiny annoyances, such as you can't use a dropdown value as a field for the preview page, so having a 'page type' drop down which is used to generate the url means the preview page doesn't always work. It also took a while to get the hang of locales, but we've got that working now. When building a new site, the ability to publish all content would be useful. It would also be great to be able to dump out all the data. You can do all of this using the API, but it would be nice to have it build in.
What problems is the product solving and how is that benefiting you?
We use it to build websites for our customers and allow them to manage the content efficiently. The main benefits are the rapid turnaround of beautifully designed sites that makes our customers very happy.
Recommendations to others considering the product:
Use it for a few projects - each project will increase your knowledge!
Build your content management system in minutes
What do you like best about the product?
Many content management systems focus on features and technology. GraphCMS focuses on the benefits and how we can help you get better results for your business or your customers. This focus on use to the user is what makes GraphCMS unique.
What do you dislike about the product?
A project is an excellent way to get a website up and running quickly, without a lot of extra work, but the customization is limited.
What problems is the product solving and how is that benefiting you?
I am a Freelance content writer; I help startups and SMBs solve their data management problems using graph databases. I build custom-made software solutions that are simple to implement.
Recommendations to others considering the product:
Yes
Excellent product.
What do you like best about the product?
The UI and the functionalities. Overall a good package.
What do you dislike about the product?
Integration with mobile apps via rest apis.
What problems is the product solving and how is that benefiting you?
I haven't faced any problems.
showing 641 - 650