Contentful Composable Content Platform
Contentful GmbHReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
317 reviews
from
External reviews are not included in the AWS star rating for the product.
A great content management tool for your business
What do you like best about the product?
A unified structure to collect content form all sources and publish them as per your requirements. The tool provides a power open API integration that enables you to connect with any third app. The tool also have draft and editing option available for posted and scheduled content. It also keeps track of modification history to revert any change.
What do you dislike about the product?
The program requires a developer to get the most out of it. There is no preview option available for your contents. Third party plugins like spell checker are not very efficient. Granting access to more people to work on one's content is not possible with a very difficult back end to operate correctly.
What problems is the product solving and how is that benefiting you?
The tool is very helpful, flexible and cost efficient as compared to other content management systems. It has a very clean and powerful interface. The tool also enables folder organization and supports media uploads. Sometimes we faces access problem while giving our team rights to edit content.
Recommendations to others considering the product:
It has a very clean and powerful interface. The tool also enables folder organization and supports media uploads. Sometimes we faces access problem while giving our team rights to edit content.
Great CMS tool that helped scale our website, BootUpPD.org!
What do you like best about the product?
Contentful makes it easy for our team to create and manage website content without having to worry about messing up the code! Paired with GatsbyJS, they've made website development and management easier than imaginable. They're quick to answer questions, allow for ultimate content modeling flexibility, quick querying via Graphql, and our developer loves working with them. Gone are the days of operating a headless WP, Drupal or *insert old tech here*, security updates, and complicated plugins - we use Contentful.
What do you dislike about the product?
The learning curve for those who are unfamiliar with CMS tools. The rich text editor is also something that can use some improvement.
What problems is the product solving and how is that benefiting you?
A faster, more reliable website that we can't break! A robust tool that allows for customization while maintaining structured content throughout the site.
We used Contentful for various small and mid sized projects successfully
What do you like best about the product?
Setting up a project takes minutes and then you are up and running. Also the environments mechanism makes it very easy to try out things. The UI is very easy to use.
What do you dislike about the product?
The smaller instances could provide more languages and it would be good to set permissions on content level.
What problems is the product solving and how is that benefiting you?
We create marketing microsites and corporate websites.
Great experience implementing as an agency partner
What do you like best about the product?
The best thing about Contentful is that you can truly use your content anywhere. You name the channel and Contentful will be able to deliver. It’s a welcome departure from the prescribed ‘one size fits all’ solutions you find with many CMS/DXP vendors. Contentful is almost 100% un-opinionated on how you develop your application, removing as many obstacles from the process as possible. This means our clients aspirations of a bespoke, best-in-class customer experience, that scales and adapts when they need it, can be readily achieved
What do you dislike about the product?
Some of the constructs and concepts can be a bit unfamiliar to those unfamiliar to headless CMS and require training
What problems is the product solving and how is that benefiting you?
Omni-channel delivery
Speed to market
Structured content
Flexibility and agility of technology choices
Speed to market
Structured content
Flexibility and agility of technology choices
Contenful best Headless Solution on the market.
What do you like best about the product?
Easy integration and flexibility to bild a high class user experience.
What do you dislike about the product?
The Image Optimization could be a little bit better - but great to have these build in.
What problems is the product solving and how is that benefiting you?
We build high availability digital products.
Put simply - the platform that will power the future of content
What do you like best about the product?
The flexibility of the solution! It plugs and plays so well with other best of breed solutions.
What do you dislike about the product?
There is a bit of a learning curve for those familiar with traditional CMS's.
What problems is the product solving and how is that benefiting you?
We're creating rich, engaging digital experiences on contentful, it's helped our clients accelerate speed to market, and allowed them to truly leverage their content in an omni channel way.
Recommendations to others considering the product:
Invest early in your content modelling skillsets, you want to make sure you get things right from the offset! Leverage Contentful's team & services to support this.
Decoupled enterprise tech - most effective for business leaders with go-to-market urgency
What do you like best about the product?
For firms with monolithic WCMS software and IT resource dependency, Contentful is designed to co-exist with legacy content and data repositories, and it is so popular that business leaders can design and launch new digital products without being hamstrung by legacy IT.
What do you dislike about the product?
Contentful product marketing is still more of a "tech developers love us" messaging. Contentful could do a better job of more easily describing how quickly they solve business problems for marketers, sales leadership, HR executives and digital product leaders.
What problems is the product solving and how is that benefiting you?
Digital wealth management and investing tools. We've realized super fast go-to-market time frames with helping grow revenue by having digitized services to offer to new markets.
API First, extensible headless CMS
What do you like best about the product?
There are many thing I like about Contentful. For me, what I like best about Contentful is their commitment to enhancing and maturing the product. I have witnessed significant change of the product since I first started using it in 2016.
What do you dislike about the product?
Due to Contentful's powerful content modeling capabilities, the web admin UI can become a challenge, especially when your solution involves many models. Happy to say that the admin UI continues to be enhanced and that Contentful has made serious strides forward over the last couple of years.
What problems is the product solving and how is that benefiting you?
Primarily, I've leveraged Contentful for channel agnostic experience and content management. In a previous role, the team used Contentful to manage offers and mobile app configs.
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.
showing 221 - 230