Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
674 reviews
from
External reviews are not included in the AWS star rating for the product.
Headless CMS with great content modeling features, powerful GraphQL and included CDN
What do you like best about the product?
Easy to set up and get started with. Versatile content modeling with flexible model relations and on-fly changes without the need or worry about API, GraphQL obviously, and a cherry on top - included CDN with image transformation. Oh wait, there are two cherries on top, Netlify integration being the other.
What do you dislike about the product?
The UI could use some TLC, seems like it was put together in a rush. I don't believe that developers would even notice this, but for content managers, it could take some time to get familiar with it. It's very flat, the whole screen looks like one big area but the actual entry form is just one column, with no tabs to group the content nor multiple columns. That single column is also hard to glance at and quickly find what you're looking for.
Assets feature is also quite limited. It serves the purpose but it's very low-key.
Assets feature is also quite limited. It serves the purpose but it's very low-key.
What problems is the product solving and how is that benefiting you?
GraphCMS solved my problem of having powerful, flexible, headless content management without hosting it myself. It also comes with CDN which is another functionality that I don't need to deal with.
Why would you setup your own CMS in 2021?!
What do you like best about the product?
The schema editor is fast and snappy. The generated GQL API is working as expected, migrations run swiftly and if something goes wrong, the support team will respond within minutes.
What do you dislike about the product?
Asset management is a big story of its own and while GraphCMS offers support for its inline "file uploader" asset handling can be quite painful and there aren't many options to work with assets. But that shouldn't be a feature of this kind of tool anyway - I'd love to see a deep integration with dedicated services like Cloudinary and a programmable "bridge" e.g. to query for rendering asset derivations on query time (Gatsby Image is basically doing that).
What problems is the product solving and how is that benefiting you?
We're running a meetup hosting website on GCMS and it works just fine. Creating a new event with speakers and talks is a matter of seconds and the backend is flexible enough to have fields enabled in no time.
Great balance of simplicity and power
What do you like best about the product?
GraphCMS does a great job of balancing powerful content modeling capabilities with a simple-to-use user interface.
What do you dislike about the product?
I haven’t found much to dislike about it, to be honest. I have noticed a couple of small glitches in the UI, but they were fixed with a page refresh.
What problems is the product solving and how is that benefiting you?
I run a tiny nonprofit (all-volunteers). We started with a hand-coded website and have been integrating GraphCMS recently to make it easier to keep our content (e.g., our list of volunteers) up-to-date.
Recommendations to others considering the product:
My organization’s site does not access GraphCMS’s APIs from the browser. We statically build our site. Therefore, I’m not able to attest to the speed and reliability of their APIs.
Great introduction to Headless CMS
What do you like best about the product?
Easy to get started with, pairs well with GatsbyJS, very generous quotas.
What do you dislike about the product?
honestly, no real complaints. Images/media sometimes take a bit long to handle uploading in poorer network conditions.
What problems is the product solving and how is that benefiting you?
As a freelancer, a user friendly CMS for non-technical clients is a must, and GraphCMS does the job well, while remaining flexible enough to me molded by the dev.
Recommendations to others considering the product:
If you're looking for your first Headless CMS for JAMstack projects, I highly recommend GraphCMS. Easy to use, & great support from the team.
Excellent HeadlessCMS for Gatsby
What do you like best about the product?
Easy to setup schema, add content and to get going with Gatsby. Deploy update to Netlify from directly inside interface.
Interface is clean and well thought out.
Interface is clean and well thought out.
What do you dislike about the product?
Rich text and Markdown being two separate data types, instead of using a single Markdown field to either edit raw or visually.
No ability to turn editor full screen, or even larger, for easier editing of content.
Lack of Gatsby specific tutorials for certain parts of the system. For instance, sourcing images from Markdown fields.
No ability to turn editor full screen, or even larger, for easier editing of content.
Lack of Gatsby specific tutorials for certain parts of the system. For instance, sourcing images from Markdown fields.
What problems is the product solving and how is that benefiting you?
I used it setup a very simple personal homepage with articles, pages and a few other content types, along with site settings and navigation control. It was very easy to setup and get connected. One great benefit is being able to re-build a Netlify site from right inside the content entry screen. Pretty slick.
Recommendations to others considering the product:
Signup with their Slack channel. Support was always quick and informed.
GraphCMS was a disaster.
What do you like best about the product?
The live graphql editing was a useful feature.
What do you dislike about the product?
Our experience with graphcms has been uniformly negative.
When we deployed on the platform our production site would regularly be broken due to how what is now called 'legacy graphcms' worked internally. Specifically any edits to our content would cause some kind of cache invalidation in graphcms and our entire site would go down due to being unable to access content.
Further, the way content editing works on the legacy platform was unusable by our marketing team. Specifically the way drafts worked caused content to disappear from our site b/c once an object was set to draft it would disappear from the published site.
We are extremely dissatisfied with our experience and are now faced with graphcms forcing us to do more work to migrate off of your legacy platform onto your new platform. We have 0 confidence that this work is useful or warranted based on our experience with the legacy system.
When we deployed on the platform our production site would regularly be broken due to how what is now called 'legacy graphcms' worked internally. Specifically any edits to our content would cause some kind of cache invalidation in graphcms and our entire site would go down due to being unable to access content.
Further, the way content editing works on the legacy platform was unusable by our marketing team. Specifically the way drafts worked caused content to disappear from our site b/c once an object was set to draft it would disappear from the published site.
We are extremely dissatisfied with our experience and are now faced with graphcms forcing us to do more work to migrate off of your legacy platform onto your new platform. We have 0 confidence that this work is useful or warranted based on our experience with the legacy system.
What problems is the product solving and how is that benefiting you?
We intended to solve the classic content management problem but instead where faced with a terrible experience of a broken site we couldn't edit.
Modern, versatile, and keeps getting better
What do you like best about the product?
The product is incredibly versatile. It's basically a cloud-based database with a nice UI and a GraphQL API.
The support is outstanding, very fast and helpful.
On top of that, we get new (and useful) features basically every month.
You get a built-in CDN which ensures fast content delivery.
The support is outstanding, very fast and helpful.
On top of that, we get new (and useful) features basically every month.
You get a built-in CDN which ensures fast content delivery.
What do you dislike about the product?
The UI can be a bit challenging for non-technical users. If someone is purely a content editor, they definitely need some time to wrap their head around it and to learn which parts they can ignore.
Sometimes things are not very polished or a bit broken for certain cases, probably because of the fast paced development. But so far it has never affected our production systems, and never been unrecoverable. The great support team always helps managing these cases and bugs are fixed quickly.
Sometimes things are not very polished or a bit broken for certain cases, probably because of the fast paced development. But so far it has never affected our production systems, and never been unrecoverable. The great support team always helps managing these cases and bugs are fixed quickly.
What problems is the product solving and how is that benefiting you?
Mostly building websites with content that is modifiable by editors. Being able to define your own schema with nested models and relations makes for endless flexibility.
We're also maintaining an internal EAM-database of IT components which we query and visualize in different ways.
We're also maintaining an internal EAM-database of IT components which we query and visualize in different ways.
Great headless CMS, especially the new environment!
What do you like best about the product?
The support is always fast and helpful! Really skilled and enthusiastic people.
What do you dislike about the product?
Legacy environment was somehow limited at first
What problems is the product solving and how is that benefiting you?
Creating a Gatsby/React website that can be maintained by non-technical people
Maximum Flexibility
What do you like best about the product?
Im astound by the unlimited data structuring possibilities through "Models" and the the ability to change the content structures on the go! The GraphQL Union Types and the relational connections between models enables me to take full control over the site structure at build time.
Content managers can easily decide where and how sections of the page are positioned.
I would like to emphasize the astoundingly quick support. My questions are answered in realtime! And the support team asks me proactive, if I was able to resolve my issues. The team publishes new features on a constant basis and they are open to new suggestions too.
If people are not sure if this CMS is something for them, they should take the advantage of the free tier and try it themself.
Content managers can easily decide where and how sections of the page are positioned.
I would like to emphasize the astoundingly quick support. My questions are answered in realtime! And the support team asks me proactive, if I was able to resolve my issues. The team publishes new features on a constant basis and they are open to new suggestions too.
If people are not sure if this CMS is something for them, they should take the advantage of the free tier and try it themself.
What do you dislike about the product?
At the current moment its not possible to prevent certain users from editing specific models, but this is not going to be the case for long. The team is already working on it.
What problems is the product solving and how is that benefiting you?
With this CMS the communication need between the content managers and the frontend developers was almost removed. Content managers are not only in charge over the content but also over the site structure.
Unlimited data modelling capability, very clean interface for editors
What do you like best about the product?
We use GraphCMS for most of our client projects. We prefer the tool as our main CMS since the Content and Management API offer us a lot of options in regard to the frontend, the performance is great and the content modelling intuitive. As an agency, we use it for projects ranging from marketing websites to machine to machine applications.
What do you dislike about the product?
From the developer perspective, the product is a game changer, nothing to complain here. Content editors need a few days to get used to the interface. The content editing experience has still some flaws - nothing major but could be improved.
What problems is the product solving and how is that benefiting you?
We are using it for several clients and the range of the solution is wide. Examples: multi-language websites with thousands of articles, pages and inter-references; structured data for machine to machine integrations . Overall, the unlimited data structuring possibilities are one big plus. At the same time, the clean interface and the well-documented APIs help us to build on micro-service architecture appropriate for each and every customer project we get.
showing 651 - 660