The benefits are mostly laid out in the pros. To summarize though, I'd say that the biggest benefits are how insanely fast we can now build CMS based products at Blazity. The development time for both the initial prototypes and production versions is substantially shorter thanks to GraphCMS and it's wonderful API.

The ease of use, slick design, powerful features (and how fast the new ones are being added in) and the fact that everything simply is a GraphQL endpoint makes graphcms a real alternative for wordpress and other cms solutions. every single one of our projects that requires a CMS is making it's way to GraphCMS as of writing this. Godspeed!

The only thing that really bothered me with GraphCMS is that the customizability and extensibility of it is limited right now. Fortunately it's changing now and the webapp is getting open sourced!

For me, it is a good and lovely CMS that in addition to Flexibility to customizing schemas, Stunning GraphQL API with powerful query and mutation facilities. My overall experience with GraphCMS Excellent customer support

I like Headless CMS features, Experience a new generation of advanced CMS with modern technologies. In addition to it has many smart features, it is very fast and agile. The support team is also a great professional and excellent friendly team.

Rich Text editor has some issues and must be solved ASAP.‌ Out of this issue , the rest are all good and excellent.

We created a collection of data that could be associated with other information as parents, a kid, or, sometimes in strange circumstances, both. This was made simple by the GraphCMS connections. We don't need distinct CMSs like WordPress when we use the graph content management system. I may now handle all cms material with the graph content management system. GraphCMS is an excellent headless CMS. It assists me in developing concise GraphQL queries and testing them in a snap. That's far superior to my prior encounter with WordPress. If you are looking for a WordPress substitute, you should consider graph CMS. It is absolutely what everyone needs from a headless CMS. A recommended headless CMS tool.

It's quick and easy to use. I appreciate that the web facilities for maintaining the simulations are responsive (both in terms of responsiveness and browsing) and do not need a high learning curve in the beginning. I enjoy its UI, its clear object-based paradigm, and its flexibility to reuse material across several versions. The API workshop is also extremely handy, particularly with pre-populated data. We wish to provide blogs and other interactive material on our website, but we also need non-tech staff from the advertising and sales departments to be capable of changing it. And, because we didn't like to design our personal CMS, it is the ideal middle ground answer.

The following are the issues that I despise the most. Migration of data from one context to another is not permitted. Over the process of adding material, we discovered some flaws. It'll be chaos if we add material in two distinct windows in the browser. Physically reload the panel to see the updated content. There are no adequate video instructions. I don't enjoy the first task page: I think it’s very worthless for expert people — I guess, it makes a perfect reason to enroll new people, however as I become more acquainted with the system, I'd prefer more detailed info.

This has been a great experience coming off of other headless CMSs that were overcomplicated, too expensive, or lacking in developer friendly features. We converted our existing NextJS website to pull content from this CMS at build time.

The GraphQL API, slick schema designer, rich set of built in types, and fast UI all come together into a powerful system for content management.

Rich text editing and collaborative editing are lacking, simplistic or non-existent. Non-technical content writers will find it hard to use at first and lacking some of the content formatting tools they are used too.

My team needed a scalable headless CMS for our homepage, company blog, and all of our periodic content. Why we chose GraphCMS: rich-text visual editor, easy-to-use localization feature (our content is in 11 languages), scalability (several hundred thousand visitors per month) and the ability to write content into the CMS programmatically (awesome for importing content from other systems). Although our front-end design was ready before we chose GraphCMS, the integration was effortless and fast.

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

Our team uses GraphCMS to push breaking news stories to our project’s webpage. The project is a part of a large non-profit initiative and the goal is to feature current content (news stories, celebrity endorsements). Authors are able to quickly add content to the CMS without sacrificing the high quality our readers expect.

Speaking from the author’s perspective, GraphCMS works really well for our project. We needed a straightforward headless CMS that could be set up very quickly. It allows content creators without any technical knowledge to easily write and publish articles – without bothering our developers. The pre-defined roles and the visual text editor are central to our workflow.

The project dashboard is very developer-focused. It would be nice to have more information for editors like recently published articles or articles for review.

My company (a software development house) uses GraphCMS for both our own website built with Gatsby and GraphCMS and for customer projects incl. native mobile apps and progressive web apps.

Designing new content architecture is super fast and easy with GraphCMS. We are building heavily for mobile devices, so using GraphQL for our content APIs is really helping our app performance. Our developers also love the code autocomplete function and the self-generated API documentation in the API Explorer. Quite intuitive UI for business users.

You need to get used to the “headless” way in order to use the system’s full potential.

GraphCMS is just so easy to use. Creating new data models and populating them for use on the front end is intuitive and the interface is very clean. The product is designed in a way that it's obvious they were thinking about their users. The biggest thing I was looking for was a data store that would be easy for a non-technical person to use while still providing customization for me as a developer and GraphCMS hits all the points I was looking for in those areas.

Every once in a while you will need to manually refresh the dashboard for new content to appear, mainly if you're adding many small data objects in quick succession - it's not a huge issue as long as you think to refresh and don't create duplicates. Other than that the performance is very good.

I use GraphCMS to prototype GraphQL schemas, as well as for all my GraphQL app/db that isn't tenant.

I love the flexibility of GraphCMS. It's meant to be a headless CMS, and it thrives at that, but don't get it twisted. GraphCMS can be a super powerful GraphQL database. I use it for my administrative tables, as well as for other projects.

In order to fully take advantage of GraphCMS' flexibility for app development, there needs to be a better authentication layer. You *CAN* achieve this with schema stitching, but it is esoteric and cumbersome.

I was impressed by how easy it is to structure and organize content with GraphCMS. Localization API is amazing. The free version is available, but enterprise plans include some advanced functionality.

I didn't gey any bad impressions on this CMS.

Ease of use, flexible, price and simple iOS integration.

"Search for filters" still needs work, especially when there is a lot of content.