GraphCMS

What do you like best?

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.

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.

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.

What do you like best?

GraphQL CMS is easy to work with. Our developers are very happy to work with this tool - everything is fast and efficient. And I personally think: GraphCMS provides the best support I ever had with any other tool.

The constant updates are great and the GraphCMS developers are always open for new features wishes of our clients :)

Well, sometimes it is hard for useres to adapt in ths modell of cms. But it really depense on the person and their exerience.

GraphCMS makes it very easy to implement new content and build new pages fast and reliable. We realized very different project with very different way to provide content on their sites - but every time it was easy to use and easy to implement.

What do you like best?

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.

It's easy to use. Intuitive and makes business sense. I can't wait to see where they take this awesome 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.

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.

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!

What do you like best?

When I first touched it, it was difficult to understand.

However, after understanding the mechanism, I feel that it is easy to understand UI and UX.

However, personally I would be happy if there were many more examples.

The window from the right side to enter data after defining the schema is small.

I want to input more widely.

I intend to provide development around GraphCMS.

My customers will use GraphCMS.

The number is still small but will increase from now on

Japanese web marketing is behind the world.

This is because there is no mechanism for individual learning.

I made a React template that works with a combination of Firebase and GraphCMS

Easily set up a member-based web service

We offer you a site to personally try web marketing.

What do you like best?

Having a native GraphQL CMS makes everything much easier to work with. Integrating webhooks and maintaining 10+ locales is seamless fo rus. Developers are much more efficient when building requests, and the product team has granular visibility over every integration step. 10/10 Support as well!

They have constant product updates and periodic feature updates with a very well maintained feedback submission system.

It would be nice to have a few more custom roles for each individual contributor we work with, but its possible to circumvent this on the frontend with our own authentication permissions.

Another nice-to-have would be integrations, but from their public roadmap I can see its being actively worked on.

Terrific support team and fantastic product. If they keep up this way there's no real need to switch.

We maintain about 10+ locales with the content for each managed in different locations. GraphCMS makes it much easier for us to structure the content needs for each website with granular accuracy. Their documentation is top notch to have a perfect implementation with React making it much faster to implement changes or new projects compared to other alternatives we've used in the past.

What do you like best?

We love the crisp UI and the simple implementations. The entire migration of 3 websites and 2 mobile apps took a matter of weeks, and the scalability is brilliant. From all the CMSs we used, GraphCMS had the best internal feedback - frontend is thrilled with GQL and our marketing team loves the editor. And their support is top notch!

The interface looks a little dated but incremental updates trickle by. There's a few features missing, however they have an open feature request board that's updated regularly and taken into consideration.

Its lean and quick to setup, we've had no issues even with enterprise level demands, however be aware that Gcms is still implementing a lot of updates since they're relatively young on the market, however most definitely in the right direction. They're not an AEM at the moment (thankfully) but are still capable of delivering the same capability.

Centralised all our content for our sites and apps into one hub, which makes it much easier to manage content for all our platforms. Frontend doesn't need to hassle backend for API maintenance, and marketing doesn't need to constantly approach frontend for debugging or deploying updates.

What do you like best?

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.

What do you like best?

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.

What do you like best?

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.

Understand why and what you can use headless CMS for first. Then read example doc on making graph queries. You will be pretty much set from there.

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.

What do you like best?

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

It is simple to use, and provide a good GraphQL API well structured for dealing with custom, rich data for both web, and mobile solutions, it has a very handy set of statistics.

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.