What do you like best about the product?

Contentful is strongest in offering structured content models for developers to query and consume via APIs. This is especially powerful when managing content across platforms such as web and mobile. The headless CMS allows flexibility in site or app hosting & implementation.

What do you dislike about the product?

Because how models are used and rendered depends on the quality of the data modeling work, and the quality of the client implementations, this can lead to a lot of complexity and it being unclear to the Contentful user how to configure the content models to get a desired site behavior. This is not inherent to Contentful, but a risk that the greater abstraction of the content makes possible. Put some real thought into how content is modeled in Contentful, and keep it simple.

What problems is the product solving and how is that benefiting you?

Prevents us from having to manage and support a CMS. Allows us flexibility in how we use our content and host code using our content.

What do you like best about the product?

Contentful is incredibly easy to use, making it a go-to CMS for both developers and content managers. Its API-first approach ensures seamless integrations with a wide range of other systems, allowing for high interoperability. I've leveraged it across various companies and clients for a diverse range of use cases, and it consistently delivers. As a truly composable technology, it gives teams the flexibility to build exactly what they need, whether it's for a simple site or a more complex, content-driven application.

What do you dislike about the product?

While Contentful excels in many areas, the pricing structure can become a consideration as you scale. As your content and API usage grow, costs can quickly escalate, which may be a challenge for some organizations when scaling larger applications or content-heavy platforms.

What problems is the product solving and how is that benefiting you?

Contentful is instrumental in acting as the enterprise source of truth for managing content at scale. It allows teams across different departments and channels to collaborate and operationalize their content strategies effectively. For me, the most value lies in the speed to market and time to value it brings to our customers, enabling businesses to extract more value from their content investments much faster.

What do you like best about the product?

As a Localization Manager, I appreciate how easily different language versions can be added to each Contentful entry.

What do you dislike about the product?

Having to publish the entries for all languages at once.

What problems is the product solving and how is that benefiting you?

It helps us to streamline the localization of our Help Center.

What do you like best about the product?

Contentful seems to be very developer-oriented in its in-depth features, and the way they are presented. The new Studio experience seems quite exciting, and should make the solution a lot easier to use.

Integrating the main Contentful API with our website build system was incredibly straightforward.

The support team (once you're a prospect or a paying customer) are very responsive, quick, and helpful. This even extends to their Engineering team being available to look at issues on their open source repos.

What do you dislike about the product?

While the developer-facing features are top-notch, the actual content authoring experience is frankly sub-par, particularly for an enterprise oriented platform like this.

There are frankly no collaboration features to speak of, and it's too easy for multiple authors to accidentally overwrite each others' changes. Commenting can only be done a field level (so if the field is, say, a very long textarea, it's not very useful).

Many features have UX complexities that make sense from a database POV, but feel clunky from an author POV. Being able to completely customise the editing interface is frequently touted as the jewel in their crown - but we found that even for simple things (e.g. allowing authors to define a custom HTML attribute for links) you'll end up having to cut a completely custom WYSIWYG editor plugin from scratch.

The sales team could only offer custom development services from their partner agencies as a solution - and so it was difficult to see the ROI on spending five figures for a licence for software we'd have to spend six figures on to develop all the missing features.

What problems is the product solving and how is that benefiting you?

We were looking to identify a solution for a headless content management, to simplify our content editing process.

What do you like best about the product?

A list of options and features that are added as part on the cms.
Customer support is a good add on.
Abbility to get integrations and options at a global level.

What do you dislike about the product?

The product is set specific and there is not much adjustability when it comes to soecific integrations hence you end us building a internal build which is a big oevrtake of maintenance.

What problems is the product solving and how is that benefiting you?

Essential web publishing efficiency.