Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Maximum Flexibility
What do you like best about the product?
Im astound by the unlimited data structuring possibilities through "Models" and the the ability to change the content structures on the go! The GraphQL Union Types and the relational connections between models enables me to take full control over the site structure at build time.
Content managers can easily decide where and how sections of the page are positioned.
I would like to emphasize the astoundingly quick support. My questions are answered in realtime! And the support team asks me proactive, if I was able to resolve my issues. The team publishes new features on a constant basis and they are open to new suggestions too.
If people are not sure if this CMS is something for them, they should take the advantage of the free tier and try it themself.
Content managers can easily decide where and how sections of the page are positioned.
I would like to emphasize the astoundingly quick support. My questions are answered in realtime! And the support team asks me proactive, if I was able to resolve my issues. The team publishes new features on a constant basis and they are open to new suggestions too.
If people are not sure if this CMS is something for them, they should take the advantage of the free tier and try it themself.
What do you dislike about the product?
At the current moment its not possible to prevent certain users from editing specific models, but this is not going to be the case for long. The team is already working on it.
What problems is the product solving and how is that benefiting you?
With this CMS the communication need between the content managers and the frontend developers was almost removed. Content managers are not only in charge over the content but also over the site structure.
- Leave a Comment |
- Mark review as helpful
Unlimited data modelling capability, very clean interface for editors
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
GraphCMS really fitted our requirements
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
We are using GraphCMS to provide content for a multi-brand site, and it has not only allowed us to build the site quickly, but has enabled us to include additional brands quickly while also allowing us to make structural content changes easily too
Recommendations to others considering the product:
While GraphCMS is smaller compared to many headless CMS competitors on the market, I have seen their product evolve rapidly in the past year and they have a small but passionate community that is supplemented by their excellent support.
Developing a Frontend application from their API was a dream, and their documentation is extensive.
Developing a Frontend application from their API was a dream, and their documentation is extensive.
Fast, enables ability to go fully typed full stack
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
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.
What problems is the product solving and how is that benefiting you?
The biggest thing we’re currently using it for is as a CMS for our website. As the web ecosystem we use is built with ReasonML, we are trying to stay as type-safe as possible. Having a schema generated that is then interpreted by the compiler minimizes the risk of getting runtime bugs.
Recommendations to others considering the product:
If the call has been made to work with a GraphQL implementation, we would recommend simply trying it out. As long as the schemas are the same, it could be as simple as swapping out a URL to try it out. It took us all about half an hour to switch our website scaffold from CMS to CMS.
The single best stack decision I've made
What do you like best about the product?
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.
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.
What do you dislike about the 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.
What problems is the product solving and how is that benefiting you?
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!
Recommendations to others considering the product:
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.
GraphCMS is a great tool
What do you like best about the product?
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 :)
The constant updates are great and the GraphCMS developers are always open for new features wishes of our clients :)
What do you dislike about the product?
Well, sometimes it is hard for useres to adapt in ths modell of cms. But it really depense on the person and their exerience.
What problems is the product solving and how is that benefiting you?
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.
Finally a Headless cms that delivered
What do you like best about the product?
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.
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
We run 10+ websites for our hotels in multiple countries and use Graphcms as our database to distribute content, offers, inventory, and promotions across all sites and landing pages.
Recommendations to others considering the product:
They have very good support but I would suggest to have a strong technical team in house since it is a more technical product unlike older cms, but this is for Headless cms in general.
JAMStack development experience and user experience
What do you like best about the product?
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.
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.
What do you dislike about the product?
The window from the right side to enter data after defining the schema is small.
I want to input more widely.
I want to input more widely.
What problems is the product solving and how is that benefiting you?
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.
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.
Recommendations to others considering the product:
I intend to provide development around GraphCMS.
My customers will use GraphCMS.
The number is still small but will increase from now on
My customers will use GraphCMS.
The number is still small but will increase from now on
A dream to work with GraphCMS
What do you like best about the product?
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.
They have constant product updates and periodic feature updates with a very well maintained feedback submission system.
What do you dislike about the product?
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.
Another nice-to-have would be integrations, but from their public roadmap I can see its being actively worked on.
What problems is the product solving and how is that benefiting you?
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.
Recommendations to others considering the product:
Terrific support team and fantastic product. If they keep up this way there's no real need to switch.
Finally a CMS bridging the dev<>mkt gap!
What do you like best about the product?
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!
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
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.
Recommendations to others considering the product:
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.
showing 471 - 480