Contentful Reviews: 4.3/5 — Solid Choice

I like the user interface. It's smooth, and the options with which to filter are lovely.

I don't particularly appreciate that there are a lot of different types of resources, like entries, assets, etc., and to a new user, this isn't very clear.

Contentful is much better than other CMS platforms, and creating internal apps to work with Contentful is does not involve too much work.

Nimbleness, Agile & the best part is SaaS, API Driven & evergrowing library of Extensions. For ex., we started our journey of Contentful in 2018, since then lot has been improved & Contentful has become more suitable for enterprises with improved scalability of API Calls etc.,

Not much to dislike, but probably they are missing the bells & whistles like Full multilevel User Management, Personalization integrations, etc.,

We have migrated 100 plus brand websites which are informal brand digital presence, where we don't need big box CMS features & don't need to install ourselves & manage the infrastructure.

I like the intuitive design that makes the learning curve much less.

I think some areas could use better descriptions of what each field is for.

We use Contentful to post to our website. It's very user-friendly.

Easy to use for all my team members, including different skillsets.

At this moment, we do not have any issues.

Time to market to share content in multiple formats to our audiences

API based content modeling, which is application-agnostic allowing to focus on content rather than how it is rendered

losing the convenience of WYSIWYG of traditional CMS

replacing current headless custom made CMS with contentful which provides out of the box support for modularisation, image CDN, on-the-fly static page generation, etc.

Not provided

Not provided

Not provided

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.

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.

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.

The concept of using this in an implementation is straightforward and solves a number of use cases.

It should have documentation on a number of complex custom implementations too.

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.

Contentful is super easy to get started with and works out of the box. It also has amazing Developer Experience!

Changing a content model is hard. I think that something like example content models would be helpful.

We're building a blog system using Contentful.

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.

We find it has limited validation rules and that the paid plan is quite pricey.

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².

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.

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.

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.

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.

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.

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.

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.

Image uploading can be painful and requires it to be done one by one manually. Ability to export views would be useful.

The cloud-based platform is crucial to having our team members access and publish remotely.

We successfully migrated from word press to Contentful. I like how easy to use it is for our marketing department to make updates to our website. It is seamless and requires no additional deployments for copy/image changes.

As a smaller business, there is no middle tier to using Contentful. You either use the free version, or pay for large scale enterprise use, which is too much. It would be helpful if there was a middle solution to allow for expanded use.

We no longer have to make deployments to dev, staging, then to production for every small change. We were able to make templates which marketing could easily make changes to at any time. Marketing also no longer needs to depend on tech deployments.

Contentful has such a great API and content modeling system. Everything feels seamless and smooth.

The API docs could be improved. Also, the rich text editor could have slightly more options like text alignment.

Not using Wordpress

I like it a lot because it is an excellent way to manage a website giving users flexibility and an extremely simple interface. to modify the content by adding text or images to personalized taste and thus give a better identity to the site

The only thing is that there is no present support to support with the use of the tool

It has helped us a lot in the matter of the administration of our content since it is possible to eliminate, edit and modify this content to have a better use of time and also it has helped us to have the best configuration to have monitored our site

Contentful is very easy to use and understand, even if you have never used it before. It gives the ability to customize and save templates, so every simple and specific action can be done in just a couple of minutes. Besides, it has a high level of flexibility, so you can structure your data in any way you want and it is a secured platform, counting with a very reliable system of verification and control of input entries.

To be honest, I have never encountered an issue with Contentful. Maybe it’s because I use it only for some basic activities, which are done quickly by using the templates. However, some of my colleagues have told me its biggest issue has to do with integration, because it doesn’t support many solutions.

In my organization, Contentful is used across several departments, but it is specially deployed in the Marketing Department for building web pages and store content libraries. Before Contentful was purchased by my company, the backlog of development had to be done manually, taking a lot of time and effort for the team. Now it can be completely done in a couple of minutes.

Model creation with the available wide variety of field types is great. The basic Markdown text field editor covers lots of use cases. Resizing images by just adding optional query parameters to the URL is magic. The content model is very flexible.

The Contentful content model is flexible, I'd even say too flexible for a simple paged website. It takes a while to grasp the Contentful-way of thinking about content. Not being able to categorize Models hurts in discoverability and creates a mess that can only be salvaged by namespacing them (e.g. "Page - Home ", "Page - About ") and then filtering ("Save as view" helps a lot here). It doesn't seem as easy to edit for laypeople as say WordPress, but I can't back that up. Multilanguage editing view could be improved I feel, displaying all languages at once can be overwhelming.

Built a non-profit flyer-type website.

Flexible price plan that fits with every business size. Provides data on any platform Out there. It is simiple to customize creative Connect then share with colleagues.

It doesn't show how the finished content will be displayed live.

Using this product gives our company several ways to manage web contents and store images and documents for online use.

Honestly, this has made managing my content a lot easier. I am just tech savy enough to use this software, if i'm being honest. With some internet searching, and some high quality graphics. my website is looking a lot sharper and I am able to deliver much better customer experience.

I feel like it is hard for me and my cofounder to stay communicated on what we are changing and how to control our variations.

It requires A LOT less time to manage, update, and build our beautiful website. It has me spending a lot less time managing the site and uploading/dealing with content and a lot more with our customers and our product.

Very clear and straightforward. At first I didn’t know what an API is, but now I’m a pro at delivering content to all of my devices, such as my iPhone, which is what I am using now, and my Windows computer.

The setup process was a bit tedious and hard for me to understand. I wasn’t sure about where the app/software was on my devices once I installed it. I had to Google my issue to solve it.

I had an issue delivering content to people’s devices for the last superbowl and clients were super angry. Now I’ve figured out a way to do so for the next time around.

I like how easy it is to create any content just using drag-drop feature and easy text editing.

It is not the best tool to make an integration with Cloud systems, such as AWS or Salesforce. It requires additional tools for the integration

It helped me to build web-sites without adding much effort. Content of the web-site was clean and neat. I would say it is a great tool for the businesses with minimum number of developers

The software was very quick to implement and get off the ground running quickly. We were demoing within the first week of use. The cloud-based platform is crucial to having our team members access and publish remotely. Loads quickly, and the API is easy to use.

Image uploading can be painful and requires it to be done one by one manually. Home page could be more useful, but it's a minor ocmplaint

We are trying to use Contentful for our hospital PR content management with public out reach.

The way to use this infrastructure to build a successful business plan for any company

The simple graphic of the website but is not a problem basically

The possibility to create a content dedicated to my exigence and to grow up the business when I need to receive more visibility

Compared to its competitors, Contentful has an extremely intuitive design, making it extremely easy to deploy to deploy a CMS environment/service in an instant. Contentful has extensive API integrations and support. It's design has lots of flexibility in-mind, making it a really good candidate for many

Contentful is expensive. A bit more expensive than any of its competitors, and it is tough to encourage early-stage companies/startups to use services like this, despite them being able to move forward products forward extremely quickly.

We used Contentful as a content management system for custom landing pages of micro-campaigns, and to build a few side-project applications that helped us progress with our core applications.

Provides lot of tools for developing applications in a easy manner

There is nothing in specific about the software to dislike

Application development

The clean of dashboard and a intuitive navigation.

I'm just testing. Until now I have a good feeling with soft.

Easy to build an app..

Straightforward interface that is easy for most any team member to use when needed.

Markdown text is difficult to read when trying to edit within the GUI. Not awful, but can be tiresome after awhile.

We use Contentful to house our database model and objects. It stores our content, easily delivers info to JSON files, and hooks into S3. Pretty simple to make updates, but, for the complexity of our web app, we have to do a lot of backend work that, often, needs a person to go through and update. However, we developed an API that syncs content from 3rd party documents that now updates our Contentful instance when content areas are unequal. Definitely useful in that way. TLDR: Contenful is simple for most end users to get the basics, advanced for developers to use for data models, and delivers data to JSON and servers quickly and efficiently.

How customizable it is. You can either use it lightly or make it like a really complex powerhouse database.

How early decisions you make about your content models can make or break your experience.

It allows our sites authors/editors to contribute without needing to write code.

I like that once you create a module or component it's easy to reuse and modify

Sometimes too rigid, and I don't like clicking through a million layers to get to a component.

We have a complex website that contentful allows many types of users to keep updated