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.
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.
GraphCMS really fitted our requirements
What do you like best about the product?
The ability to change content structures on the fly, without affecting the API, and the ability to manage different development lifecycles within the same content project. The support is also amazing and responsive, and it is good to see the product constantly evolving and improving.
What do you dislike about the product?
We have a few niggles with the richtext editor, but because they are constantly improving I believe this is an area they are looking to work on.
What problems is the product solving and how is that benefiting you?
We are using GraphCMS to provide content for a multi-brand site, and it has not only allowed us to build the site quickly, but has enabled us to include additional brands quickly while also allowing us to make structural content changes easily too
Recommendations to others considering the product:
While GraphCMS is smaller compared to many headless CMS competitors on the market, I have seen their product evolve rapidly in the past year and they have a small but passionate community that is supplemented by their excellent support.
Developing a Frontend application from their API was a dream, and their documentation is extensive.
Developing a Frontend application from their API was a dream, and their documentation is extensive.
Fast, enables ability to go fully typed full stack
What do you like best about the product?
We use ReasonML in our frontend and website. It’s an ML-based language with static type checking. Combined with GraphQL, it gives us the ability to import a schema using an introspection query, which in turn gives us the ability to do compile-time type checking. Contrary to similar services, GraphCMS implements those introspections—a huge win for us.
Another huge win is speed. We’ve found GraphCMS appears to be much faster compared to similar services.
Apart from that, we’ve found the platform to be quite flexible. Being able to not only specify relationships between content, but also the way it relates to other parts of the schema (one-to-one, one-to-many, etc.), makes for great control over the schema. We’ve internally started using it for prototypes that go beyond the scope of a simple CMS because of this flexibility.
Another huge win is speed. We’ve found GraphCMS appears to be much faster compared to similar services.
Apart from that, we’ve found the platform to be quite flexible. Being able to not only specify relationships between content, but also the way it relates to other parts of the schema (one-to-one, one-to-many, etc.), makes for great control over the schema. We’ve internally started using it for prototypes that go beyond the scope of a simple CMS because of this flexibility.
What do you dislike about the product?
We feel the interface could be slightly more tailored for content managers, as it seems more tailored towards developers now.
Another (minor) thing is that we did not find a repeatable item field. While this is something that is easily solved with relationships (and sometimes maybe even beneficial to do so), there are other cases, specifically when dealing with things like pricing tables, or a list of features (in other terms; things that will only ever be shown in the context of their parent entity), where it may be much clearer to the content manager to communicate that the item can occur multiple times.
Another (minor) thing is that we did not find a repeatable item field. While this is something that is easily solved with relationships (and sometimes maybe even beneficial to do so), there are other cases, specifically when dealing with things like pricing tables, or a list of features (in other terms; things that will only ever be shown in the context of their parent entity), where it may be much clearer to the content manager to communicate that the item can occur multiple times.
What problems is the product solving and how is that benefiting you?
The biggest thing we’re currently using it for is as a CMS for our website. As the web ecosystem we use is built with ReasonML, we are trying to stay as type-safe as possible. Having a schema generated that is then interpreted by the compiler minimizes the risk of getting runtime bugs.
Recommendations to others considering the product:
If the call has been made to work with a GraphQL implementation, we would recommend simply trying it out. As long as the schemas are the same, it could be as simple as swapping out a URL to try it out. It took us all about half an hour to switch our website scaffold from CMS to CMS.
The single best stack decision I've made
What do you like best about the product?
GraphCMS has to be the most feature-complete GQL based CMS out there. Drop any preconceptions you may have about out-of-the-box solutions and give it a spin - the depth this product has is incredible and the support from Fabian is phenomenal, even at 8.30pm on a Friday evening.
The free tier quotas are extremely generous for testing purposes and you could easily run a small project with no costs. The pricing scheme is well documented and extremely generous considering the A* support they give, the amount of effort gone into their documentation and the knowledge of their staff.
The free tier quotas are extremely generous for testing purposes and you could easily run a small project with no costs. The pricing scheme is well documented and extremely generous considering the A* support they give, the amount of effort gone into their documentation and the knowledge of their staff.
What do you dislike about the product?
Webhooks are locked behind the paid tier, which, if you rely on them, requires you to take a dive into your wallet to access. That being said, now that we're ready to scale, it's a non-issue. Some CMS focus more on the author experience so if you're looking for a headless blogging platform such Ghost, you may not find what you want here. Saying that, I would 100% recommend trying it before coming to any conclusions.
What problems is the product solving and how is that benefiting you?
With JAMstack becoming ever more popular, we tasked ourselves with building a scalable, revenue-driving app with minimal overheads and effort required. GraphCMS was integral to this and as is definitely our go-to choice!
Recommendations to others considering the product:
Try it. There's nothing to lose and the potential benefits are huge. Do yourself a favour and join the slack - Whilst it isn't heaving with chatter, the support you can grab there when you have a question is second-to-none and extremely quick.
showing 681 - 690