Contentful Composable Content Platform
Contentful Inc.External reviews
326 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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.
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.
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.
Great pick for a JAMStack CMS
What do you like best about the product?
One of the more user-friendly CMS's out there. Really a joy to use and easy to understand. Create new content models and content is simple and intuitive.
What do you dislike about the product?
The only thing that confused me was lack of single-use type entries.
What problems is the product solving and how is that benefiting you?
We use it to run a marketing site.
Its just quick and meaningful to get data dynamically in your hands
What do you like best about the product?
Its content models and easy to understand content handling. It simply makes sense of how the data is arranged in a meaningful way. The image and data caching logic are also good. At the client-side, a strong code base is required to get the most out of the contentful. We were fortunate to make this happening in our project.
What do you dislike about the product?
More abstraction, markup support within the contentful and proper sorting and filtering strategy. In the content modeling, how one content model can relate to others. In terms of markup support, this was mostly observed during our project development that the markdown support library does not work as expected so we need overriding to get how it looks in the contentful preview window.
Proper sorting and filtering in terms of datasets creation time. Usually, if a huge amount of data has been added in one day. I need to go and look at every content model and can't find what's been added in that one day.
Another problem, in terms of logging the changes done on a particular record. Sometimes, 100 people change data in a day. I cannot see who has changed what and no logs or history is there in the content model or data side. There are different scenarios where we face issues, in a large team of developers and testers when they start changing, some should keep an eye on what is changing. That way we faced problems during the whole process of development.
Proper sorting and filtering in terms of datasets creation time. Usually, if a huge amount of data has been added in one day. I need to go and look at every content model and can't find what's been added in that one day.
Another problem, in terms of logging the changes done on a particular record. Sometimes, 100 people change data in a day. I cannot see who has changed what and no logs or history is there in the content model or data side. There are different scenarios where we face issues, in a large team of developers and testers when they start changing, some should keep an eye on what is changing. That way we faced problems during the whole process of development.
What problems is the product solving and how is that benefiting you?
The problem of dynamic data. Mostly client-side applications want to get rid of data handling. Contentful is a great savior in this. All the configurations, data handling and quick response from the backend help client-side applications to get faster. Syncing is also good. Keeping applications up and running. However most of the time it's difficult to understand the error handling if something is changed and the client-side starts getting crashed.
Recommendations to others considering the product:
It's a very cool and fastest CMS I have ever worked with. The concept of spaces and content modeling is pretty much required in most of the organizations and there are different stakeholders that can get the benefit from the way contentful works.
Awesome and super flexible CMS
What do you like best about the product?
I love the flexibility of contentful. It gives you all the freedom that you need to create amazing apps. Working with the Webapp is lots of fun. It's simple to use, fast and you can collaborate with a big team and manage multiple languages in a simple way. In combination with gatsby an amazing stack to build fast, modern sites!
What do you dislike about the product?
With great power comes great responsibility. Since contentful is so flexible, you certainly need some experience to get the most out of it. It takes a bit of time to fully understand all concepts from content types to internationalization but it is worth learning it and the resources on the website (plus learning center) make the learning efficient and fun.
What problems is the product solving and how is that benefiting you?
I want fast and user friendly websites and the combination of gatsby + contentful gives me exactly this. Plus, our project is multilingual and we need to be able to add new languages without too much effort and be able to manage content in a bigger team. Another advantage is that we are going to manage several Apps through one CMS.
Recommendations to others considering the product:
Make sure to have an experienced enough product team and invest time into understanding the core concepts before starting to build your content structure.
Content structure for the creation of websites
What do you like best about the product?
It allows you to add new content models very easily, it is a very intuitive and easy-to-use application aimed at beginners, in the same way it easily integrates with other modalities, including a basic text editor and its content model is really flexible, by What is characterized by being an application that helps me when automating content creation.
What do you dislike about the product?
Sometimes it takes too long to update the changes that are made in the preview pages, which greatly delays us in the activities that depend on these actions because there is clearly nothing left to wait for them to load and as I mentioned is a Very slow process, about 1 hour or maybe more.
What problems is the product solving and how is that benefiting you?
It is an application that provides us with a content structure to be able to promote websites, applications and devices, thus facilitating the creation of professional content in an automated way thanks to a variety of tools as well as allowing us to share each of our creations without any type of restriction which extends our reach.
Recommendations to others considering the product:
It is an application that will adapt easily to the needs that present as a company when creating content and in this case we speak within the context that corresponds to web pages, applications or devices in the same way will be very useful when storing data to develop a project for example.
Easy to Use Content Platform
What do you like best about the product?
The software was very quick to implement and get off the ground running quickly. We were demoing within the first week of use. Loads quickly, and the API is easy to use.
What do you dislike about the product?
Image uploading can be painful and requires it to be done one by one manually. Ability to export views would be useful.
What problems is the product solving and how is that benefiting you?
The cloud-based platform is crucial to having our team members access and publish remotely.
showing 141 - 150