Contentful Composable Content Platform
Contentful Inc.Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
309 reviews
from
External reviews are not included in the AWS star rating for the product.
Contentful worked wonders for our static nonprofit site, Hack4Impact.org!
What do you like best about the product?
Above all, the GraphQL API made it super easy to add the *exact* content we want to every area of our site. We just needed to inspect our Content Models, build a query in Contentful's own playground, and copy / paste into the codebase.
We were also very impressed with the user experience. We were able to onboard designers and operation directors in 30 minutes, and they felt confident enough to write new content without coming to the devs. The "Draft" / "Published" states were easy to understand, and the rich text fields were super friendly for complex fields. Couldn't be happier overall!
We were also very impressed with the user experience. We were able to onboard designers and operation directors in 30 minutes, and they felt confident enough to write new content without coming to the devs. The "Draft" / "Published" states were easy to understand, and the rich text fields were super friendly for complex fields. Couldn't be happier overall!
What do you dislike about the product?
Our only "ask" would be template strings for passing values into our text entries. For example, being able to pass a "name" parameter to Contentful, and then using that name throughout a given content model (i.e. This is {name}'s profile picture).
What problems is the product solving and how is that benefiting you?
Basically, we needed a place to store information about our university chapters, board members, and all future content in a single place. In doing so, our content needed to be:
a) Super flexible as we add fields, text, flags, and other values
b) Easily edit-able, so designers and product managers could update content with confidence (and without the developer tickets)
In the end, Contentful delivers all of this and more!
a) Super flexible as we add fields, text, flags, and other values
b) Easily edit-able, so designers and product managers could update content with confidence (and without the developer tickets)
In the end, Contentful delivers all of this and more!
Contentful is great for specific use cases but is not magic.
What do you like best about the product?
I like the ease of creating object models and the CDN performance of serving content once you entered your data. I like that you can create clones of the data quickly for testing etc.
What do you dislike about the product?
The complexity of the generated json of the data model, especially for rich text content. Very confusing and optimized for Contentful internal reasons. They are lacking some basic features that are making the content model much harder to manage. A few examples:
1. You can’t embed object models directly in content without making them a shared object first. This is like trying to write a document and embed tables and info boxes, but be forced to create these as separate documents and link them to your document. This grows to a huge problem the larger your content grows.
2. The content management APIs and the content delivery APIs (the creation and editing vs serving content to end users) is slightly different, but just enough to make your code inconsistent and confusing between the two use-cases.
3. Lack of easy ability to apply permissions based data access for end users
4. Different SDKs (namely JS, Java and REST) are not unified enough in concepts.
5. Support is very slow. I had simple “how/why” questions answered months after I asked them.
6. Learning curve of the ask and rendering of content is quite steep.
7. Scheme migration between versions is problematics and required 3rd party tools to track your changes between a dev and production versions of your content object model.
1. You can’t embed object models directly in content without making them a shared object first. This is like trying to write a document and embed tables and info boxes, but be forced to create these as separate documents and link them to your document. This grows to a huge problem the larger your content grows.
2. The content management APIs and the content delivery APIs (the creation and editing vs serving content to end users) is slightly different, but just enough to make your code inconsistent and confusing between the two use-cases.
3. Lack of easy ability to apply permissions based data access for end users
4. Different SDKs (namely JS, Java and REST) are not unified enough in concepts.
5. Support is very slow. I had simple “how/why” questions answered months after I asked them.
6. Learning curve of the ask and rendering of content is quite steep.
7. Scheme migration between versions is problematics and required 3rd party tools to track your changes between a dev and production versions of your content object model.
What problems is the product solving and how is that benefiting you?
Storing rich text and other types of data model for rendering dynamic content in our front end application. The main benefits are the performance of the CDN backend, the robust url-based APIs to manipulate media urls (manipulation of images in ad-box / real-time for size etc) and the fact we could bootstrap our application without starting with our own backend.
Recommendations to others considering the product:
Do not assume that just by having a headless dynamic CMS it means you have full freedom of your object model. This doesn’t solve for the basic problem that any changes you make to the CMS without updating your front end to respect them can actually break your sites too easily by your content editors.
It has allowed me to manage content on various digital platforms to achieve a greater reach
What do you like best about the product?
What I like most about this tool is its stability and its user-friendly design, which allows me to use this application quite easily, it allows you to edit sections of our website in a fairly simple way In addition, it increases the efficiency and collaborative work among all the members by allowing us to work in a more efficient way.
What do you dislike about the product?
None, it seems like a very complete tool for marketing activities.
What problems is the product solving and how is that benefiting you?
It has allowed me to manage content on various digital platforms to achieve a greater reach and number of followers on my different social networks and websites.
Contentful has been an absolute game changer for us
What do you like best about the product?
Our content creators love the intuitive user interface and how quick it is to update content. Contentful is by far the best in this regard, compared to the other platforms we trialled.
Our technical team loved how quickly there were able to get started, thanks to the great JavaScript SDK and simple content modelling. The Content Delivery API is fast and reliable, it's been a key factor in bringing our average page load time down 70%.
As a NFP with a number of touch points, Contentful has been a game changer. We finally have a single repository for content that all of our sites and apps can pull from.
Our technical team loved how quickly there were able to get started, thanks to the great JavaScript SDK and simple content modelling. The Content Delivery API is fast and reliable, it's been a key factor in bringing our average page load time down 70%.
As a NFP with a number of touch points, Contentful has been a game changer. We finally have a single repository for content that all of our sites and apps can pull from.
What do you dislike about the product?
I really don't have many complaints but my one bug bear is that I wish the rich text editor had a few more options. We've had to come up with a few workarounds for things like superscript and subscript. It would also be great if we could embed Youtube videos, as you can with the markdown editor.
What problems is the product solving and how is that benefiting you?
When we started our project, we had 3 main things we wanted to address:
- Avoid duplication of content across our platforms
- Be less brittle (i.e. allow our content creators to make changes without breaking anything)
- Reduce development overhead
Contentful has exceeded our expectations in meeting all of these requirements, can't speak highly enough about the platform.
- Avoid duplication of content across our platforms
- Be less brittle (i.e. allow our content creators to make changes without breaking anything)
- Reduce development overhead
Contentful has exceeded our expectations in meeting all of these requirements, can't speak highly enough about the platform.
Recommendations to others considering the product:
If you've decided a headless CMS is the way to go for your project, look no further than Contentful.
Contentful works well and the setup was really fast
What do you like best about the product?
The setup was really fast and we were able to publish our website on 2 weeks.
Also, we are really happy with the interface to add and manage content with a good productivity.
Support teams always have a quick response time and accurate answers.
Also, we are really happy with the interface to add and manage content with a good productivity.
Support teams always have a quick response time and accurate answers.
What do you dislike about the product?
Regarding payment method, we sometime lacked another options because we had problem with our credit card. But the Billing Support team helped us until we found a solutions, so it was ok.
What problems is the product solving and how is that benefiting you?
It was faster to implement Contenful CMS than coding our own CMS. This was really important because the delivery time of the project was really short!
Easy to Implement, Super Flexible
What do you like best about the product?
The flexibility of the platform is really remarkable. From content modeling to the editor interface, you can build everything to work with your team. Their CLI tools are also really nice.
What do you dislike about the product?
Some of the 3rd party app integrations are a little clunky but otherwise no complaints.
What problems is the product solving and how is that benefiting you?
it is at the center of our media business.
Great tool for content management!
What do you like best about the product?
Our team has really enjoyed the flexibility Contentful gives us in managing our content; as a non-profit without in-house developers, it has given us the freedom to keep updating our content creatively without always needing to hire a contractor. We like how easy it is to preview content in draft mode in QA. It's great to be able to add helper text for different sections so that we can quickly onboard new users. Adding content for additional languages is easy.
What do you dislike about the product?
Sometimes it is too easy for a user to accidentally change something - but that is probably mostly a matter of training users well & how your space is set up. We would also like to have more content types, but it is possible to purchase those.
What problems is the product solving and how is that benefiting you?
We are delivering content to a wide variety of partners through a few different tools, and having many different non-technical staff members collaborate on creating and updating that content. One big benefit has been our ability to target content to certain groups and users through Contentful, and to easily add additional languages.
Recommendations to others considering the product:
It's a great tool! If building something complicated, make sure you collaborate with developers to know how many content types you will need.
Great concept for headless implementation
What do you like best about the product?
The concept of using this in an implementation is straightforward and solves a number of use cases.
What do you dislike about the product?
It should have documentation on a number of complex custom implementations too.
What problems is the product solving and how is that benefiting you?
This has helped to create a headless implementation of our CMS system. It helps to resolve a lot of dependencies in a tightly coupled system.
Very easy to get started with
What do you like best about the product?
Contentful is super easy to get started with and works out of the box. It also has amazing Developer Experience!
What do you dislike about the product?
Changing a content model is hard. I think that something like example content models would be helpful.
What problems is the product solving and how is that benefiting you?
We're building a blog system using Contentful.
Contentful helped us build a scalable platform in a few weeks and it keeps growing
What do you like best about the product?
From a content mangement side, we like the ease of use of Contentful, its multilingual support and the asset management. Technically speaking, we appreciate the ability to create custom extensions, its seamless integration with Netlify, webhooks and the API documentation and structure.
What do you dislike about the product?
We find it has limited validation rules and that the paid plan is quite pricey.
What problems is the product solving and how is that benefiting you?
Using Contentful as our headless CMS allowed us to choose the development stack we wanted: we chosed a Jamstack with Github, Netlify and Nuxt.js. It allows us to develop and test our website very quickly and thanks to pre-rendered pages, the website is blazing fast and consumes lot less C0².
Recommendations to others considering the product:
If you want to build an application without risks of being technically limited in a few months or years, Contentful will provide the needed flexibility and technical performance you’re hoping for. If a functionality does not exist, you can just build it yourself. Performance of the API is also great.
showing 221 - 230