Contentful Pricing, Features, Reviews & Comparison of Alternatives

Pros
It is impossible for users to create elements that are totally out of line with the corporate design. Contentful also loads faster than many other CMS.

Cons
There isn't much I like about Contentful. It is impossible to copy entire pages without a lot of effort, which makes it very time-consuming to create new pages. While you can re-use existing elements, the problem is that if you change them, they are changed everywhere, and there is no way to just copy an element in order to use it as a new element (i.e., changes you make to it don't affect the element you copied). As others have mentioned before, it sometimes takes a quarter of an hour for changes you made to appear on the preview pages, which is just painful (Wordpress is pretty much instant). But by far the biggest pain is that there is no way for the user to simply access the CSS. We have to go back to our engineering team for every little tweak we want, even if it is just the padding of an element or the alignment of a certain style of text. Another issue I have is that it is hard to figure out where on a new page you are while you are editing it. Unlike Wordpress, where you can see the overall structure of your page elements clearly on an overview page, you can only see the rows of the page on the overview in Contentful - you have no idea what the structure inside each row looks like until you click on it. That means you're getting disorientated quite quickly as to where you need to click to edit element X of the page. Overall, I find Contentful terrible to use. It has a few benefits, but at least from a content management user experience those don't outweigh the significant downsides at all.

Rating breakdown

Likelihood to recommend: 1/10

Pros
It is truly cloud-first for a headless approach. You can build your content model and control your input with easy validation (min/max/regex) and even dependencies on other models. It is truly headless and integration with node, react, asp.net, and php have all been relatively easy. Node was definitely the easiest integration.

Cons
I would have said migration between environments, but they recently released a solution for that. I haven't verified it but I'm excited about it. I think the other thing is dealing with deleted fields, it makes it a bit challenging that you have to remove it from view and then delete it to make sure it won't break the existing model. I also get frustrated when I make an existing field that is required and there is no notification that the content doesn't match the new criteria.

Rating breakdown

Likelihood to recommend: 9/10

Pros
stable, friendly configuration, data structure is clear, and have api auto configuration

Cons
navigation is a little bit tricky, like when duplicate an entity, it lost the original entity's position, so have to go back and track the entity again

Rating breakdown

Likelihood to recommend: 10/10

Pros
Contentful is a content management system solution which has a great API focus and allows us to develop our own data relationships and data structure. It provides us complete flexibility within projects and gives us the capacity to distribute to different types of platforms with less hassle. The user interface is straightforward and really simplifies the process for our backend system.

Cons
When used in Firefox browser, there are some occasional glitches. However, it works perfectly well in Chrome and Safari, so it’s not really a big problem. When I contacted support, they reviewed and tested it but they said it might just be a plugin issue.

Rating breakdown

Likelihood to recommend: 7/10

Pros
The UI of Contentful is superb in its own right, but especially when compared to other similar CMS interfaces. Everything is laid out neatly, and it's easy to sort and edit your content. When paired with a static site generator like Gatsby, Contentful is WAY more safe, dependable, and low-maintenance than WordPress (which I'm sad to say, after being a WP dev for years, is a complete mess).

Cons
Modeling content can be tricky at first, especially since you can't have differing fields within a content type. But once you understand the general concept of "referencing," it becomes quite easy and even enjoyable to structure nested and/or complex data.

Rating breakdown

Likelihood to recommend: 10/10