Hygraph Reviews: 4.6/5 — Highly Rated

The project setup is very straight-forward, and all process done on the Hygraph dashboard, we don't need to install any package to start the project. Other features I love the most, such as seamless integration with Next Js and even Hygraph provides rich text renderer for React to help us render smoothly in the front-end.

I hope Hygraph create new pricing to afford, because the paid version cost hundred of dollars

Hygraph helps full stack developer and content creator to set up backend service without headache so we can start project faster

They've put a lot of effort into the user experience which makes it a wonderful place to edit and manage content. The ability to pull in remote data and publish as part of the content API is also a wonderful feature.

They probably need more comprehensive examples of starter applications written in frontend frameworks (such as Nextjs). It would be great if they provided guided procedures (and tools) for migrating content from other well known CMSs such as WordPress.

Hygraph is opening the doors to future opportunities as they add more integrations to their Market Place.

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.

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.

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.

the flexibility that graphql gives us, the frontend is also well made

a tool like liquibase for a db would be useful, also the merging between branches could be better

we are using it as a headless cms and also some models are built up by users who are not db admins

The interface is very well laid out and user-friendly. The docs are very clear.

There are some advanced features missing (media domain optimization for SEO for instance), some are being introduced though.

Creating complex information architectures that can be used in different touchpoints.

Below are the things which I like the most. - The ease of use - Slick design - rich-text visual editor - Easy-to-use localization feature - Scalability - Good Speed - API integration - Support

Below are the things which I dislike the most. - Content should not migrate from one environment to another - Found the bugs during the adding the content If we add content using the 2 different tabs in the browser then it will be a mess. - Manually refresh the dashboard for new content to appear - Missing proper video tutorials

Using the graph cms we do not need individual cms like WordPress. Now I can manage all cms content using the graph cms.

GraphCMS has been great for us to have one place to store all of our content that can then feed into multiple instances of our learning system, so we can provide our content to multiple corporate clients

There are sometimes issues with content feeding from GraphCMS into our platform, where things like quizzes do not upload properly and we have to resend it or manually update in our platform

We are able to instantly upload content into our platforms with the click of a button, saving multiple hours of manual work that we would otherwise have to do, allowing us to make more sales and quicker

The most significant benefits are how fast we can now build content management systems. The development and initial prototype and live version takes less time, and things get ready rapidly fast

The only things that I wouldn't say I like it's not flexible and not extendable as much, not much customization available

I am myself, a freelance software engineer; I make apps and solve clients' data management requirements. Its make things get ready very fast

GraphCMS from the ground up has been built with both the end-user and developers in mind. It offers extensible features which allow a developer to build a CMS that reflects their needs and requirements truly while also giving and user-friendly and customizable enough UI that non-technical users are comfortable opening it up and making changes. It has a host of well support integrations with popular frameworks such as React and a community Slack team that is well moderated and always open to giving a hand just fleshing out an idea or providing debugging help with integration or developer expereince. It's a pleasure to use, and It's hard to look back to more rigid solutions.

Sometimes it can feel like the UI is rather overwhelming with all the tabs and links and slide-out pages here and there. Sometimes I can struggle to search effectively using the search bar within the UI. Also, as a developer, It'd be amiss if I didn't ask for a dark mode :)

We are building an international Shopify store while also creating expansive and additional content for our content teams to add our own flair and meta data to products. The flexibility of relationship types in GraphCms has really allowed us to ensure we have a handle on what can be placed where while also providing our content team have the flexibility to build pages as desired using content modules we've built in-house.

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.

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.

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