Marg GraphCMS

We transitioned to graphcms in about 3 months from our legacy systems and almost instantly we could tell that we made a good decision. The developers love the documentation, and enjoy the interface and the flexibility with graphql, making it very easy for them to deliver new requests and projects. The product manager has a granular view into the projects and into seeing what's going on, making it very transparent to work with.

Their webhooks feature make it very easy to integrate with all our existing services and we're easily able to localise and scale to all our key markets without worrying much.

Cannot think of anything yet - the entire process has been smooth and the functionality is as expected. It was a little difficult to integrate older hotel software but it was mostly because of a lack in documentation and support on the side of legacy platforms.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

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.

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.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

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.

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.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

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.

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.

This is a great option for a headless CMS where you need a product that is moving fast to be the best in market, if it isn’t already.

App and web content distribution