Hygraph Avis et détails du produit

GraphCMS is easy to use and has a clean UI. Schemas are fully customizable and with a great range of options. It helps to save a ton of time and work when creating new content for a website. The generated GraphQL API is exactly what we were needing for handling our content. What is also really helpful, is having a Draft and Published status for the content. We use Draft for our dev environment and Published for production, the process of updating the status to Publish is a 2 click action which is great to make fast changes.

The only downside I can find, and it's a personal preference, is that I would rather have the content listed in descending creation date order by default, instead of ascending.

My company has an entertainment website, with new-age, astrology and lifestyle articles. We save a lot of time with GraphCMS as it allows us to upload content quickly. It's also easy to delegate the creation of new content to a content manager with no technical knowledge since the UI is very friendly.

It has a great UI/UX, and a flexible Schema's design API

When dealing with images having to upload assets before being able to link theme, it would be better if we can upload images directly when we link theme

I am dealing with reach data when working with GraphCMS, structuring and editing data seems really easy, then on the mobile side consuming data using GraphQL have a huge benefit for statically typed models, and minifying the amount of data needed for each backend request.

Noob friendly guides and nice user interface to get someone set up fast.

Web Hooks aren't also free (Joking, its only fair they aren't).

Easy management of blog content and allows me to query my content using graph queries - thus I benefit in querying only the data I need at once as long as I have linked them.

- Good Support - Quick Iterations, features added frequently and they listen to the community - Great for GraphQL lovers

- Dashboard can be confusing sometimes (some data seems weird)

Doesn't need to code a backend if you need to do a static website in React. Gatsby + GraphCMS works very well.

We’re huge advocates for Graph CMS for their clean interface, staging that allows us to release easily when we want, graphQL simplicity, and the flexibility of what it allows.

I’d love some more content from them to help achieve things that we might not know are even possible or are thinking about but not necessarily know the path to achieve them.

App and web content distribution

We like the rich-text visual editor, the easy-to-use localization feature (our content is in 11 languages), GraphCMS’ scalability (several hundred thousand visitors per month) and the ability to write content into the CMS programmatically. Although our front-end design was ready before we chose GraphCMS, the integration was very fast.

GraphCMS is built to handle structured data, so its added value is lower if you are only handling freeform texts.

My team needed a scalable headless CMS for our homepage, company blog, and all of our periodic content. The set-up was very fast. Our backend developers don’t have to maintain the CMS; our frontend devs don’t need to bother the backend devs if they want to use or modify the GraphQL API.

Our engineering team loved Hygraph because of the ease implementation and the vast set of features. Our non-technical team also appreciated if because it is easy to use and make changes.

It's not the cheapest option, especially for a small team.

Hygraph allowed us to stood up a website for our business fairly quickly and allowed us to make changes on an ongoing basis really easily.

User-friendly Interface,Accurate Monitoring

probably the initial investment, not that easy to setup

easier / faster content management

As a developer, I found myself quickly being able to implement an integration with this CMS. The API playground was such a big help in this because I had no previous GraphQL experience. Also, the customer support is amazing, they reply fast and always find a workaround for your specific use case.

We have a Python backend, and there is no example on how to integrate hygraph using Python in the documentation, perhaps that could be added at some point to the github repo.

It is equally easy to use for technical and non-technical users. The interface is self-explanatory and the structures are clear. This allows a seamless, low-overhead content production and release process where the content team can work on their own terms and trust that the content will be delivered to the user in the right structure. This is also due to the very well thought-out field types and validators. From a developer perspective, those ensure that the content follows the format expected by the application, for it to be correctly displayed. It is easy to set up validators and display informative error messages shown to the content editors. This reduces back-and-forth between content teams and technical teams and keeps the content on a high quality level.

My favourite thing about Hygraph is the user interface. As a content admin this makes my experience seamless and something that I enjoy when compared to the comparatively outdated alternatives.

At times I find that the website doesn't scare in a way that I would expect. I sometimes work from my laptop away from the office and when I split screen windows not all of the ui elements fall into a place that is clear without being a maximised window.

Hygraph makes it far easier than the alternative systems that I've used before to manage content across multiple stores and product categories. It improves productivity speed and allows the team to get through vast amounts of content quickly.