Contentful Composable Content Platform

I am Niketan Naidu, working at LTIM, and I am using Contentful for our content management system and website. I have been using Contentful for three years, and it has been excellent work. We use Contentful primarily for our website content management system, with the full website built upon the content management system powered by Contentful.

We manage all pages from A to Z. We have built a page template, and for each page we create, we generate dynamic routes in the Next.js application, retrieving data from Contentful and building all the pages. It is not limited to just a product page or landing page; it encompasses all pages of the website.

We are also using Contentful SDK for space-to-space migration as provided by Contentful's powerful CLI tools. We use this for migrating assets or entries from one space to another space easily. This is a significant advantage.

Contentful's GraphQL marketplace application is excellent and useful. We can query immediately and see the results of the collections we create. Contentful also has localization features. However, I believe the only limitation is with localization; locale-specific rules and permissions are not at the extent or level we need, so we cannot provide permissions at the locale level. This is the problem.

Here is the scenario: we have multiple DDA groups that work on Contentful updates. We want a specific DDA group to work on specific Contentful content only, which can see, read, write, and delete on that specific locale only. We do not want other locale content of that space to be visible when we have multiple locales. Currently, we only have a limitation where the edit feature can be restricted to the locale, but we cannot restrict the read, delete, and create functions for that specific locale.

Contentful has provided custom roles and permissions, but in my opinion, it should be at a more extensive level, enabling us to restrict users at the locale level so that a user sees only the content of their specific locale. A user cannot see the content of any other locale if they are not provided the permission.

Content management is simplified, and team collaboration has improved. For workflow timing and content updates, there is some limitation in content updates, as manual work takes considerable time. However, most aspects—including content management, Contentful CLI tools, Contentful roles and permissions, and GraphQL query management—have positively impacted our operations. Website management has become very easy, and content updates to websites are straightforward. We can easily update the website content.

I wish Contentful would provide a better feature for publishing all content entries at once. Additionally, if any validation errors occur, handling them in a better way would be beneficial. Changing the state of entries for querying to the CLI tools would also be valuable. If Contentful could provide a better parameter for changed state entries, that would be excellent. Most importantly, the publishing option for publishing all changed entries at once would save considerable time.

I would recommend that roles and permissions be improved as soon as possible, as that would be a valuable feature.

I have been working for 4.5 years in my current field.

Contentful is very stable. I did not see any issues.

Scalability issues are handled by our organization's admin team. They will be in contact with the customer support team. If there are any issues, we report them to our organization's admin team, and they check with support.

We used Sitecore previously. We converted all websites to modern web technology using Next.js, so we switched to Contentful for the modern features.

Setup and pricing are handled by our organization's admin team. Currently, I do not have much information on this.

I would say time saved is the key ROI. With Contentful, we can migrate entries using the CLI and update content easily once we become habituated to it. Time was saved most of the time.

Setup cost and pricing are handled by our organization's admin team. Currently, I do not have much information on this.

Organizations can use localization if they have the same content and should watch out for that feature. They can use the CLI for easy migration in Contentful. Exploring more on Contentful GraphQL queries, Contentful SDK, and Contentful CLI is beneficial. Contentful web app is very easy to learn, and the learning curve is simple. It is an easy solution.

I would like to highlight the roles and permissions features. I would request the team to look into it and provide that feature, as it would be excellent. I provided this review a rating of 9.

I use Contentful to manage content-heavy websites for clients, where all content related to pages is stored, such as product pages, landing pages, and the homepage.

The preview API is used heavily, which allows editors to create pages and preview them on their machines to see how content will look on the website.

Contentful offers many features, including functioning as a headless content management system that can be integrated with any tech stack, using a CDN to deliver content which is significantly faster than serving through a single server, and providing a UI that is very easy to use, allowing users to navigate around easily and perform their normal tasks.

The most valuable feature is the headless capacity of Contentful because Nuxt is used for the front end and Shopify for back-end operations, so Contentful bridges that gap easily and allows content-heavy pages to be managed.

Contentful has helped serve clients better by allowing campaigns to be launched quickly and pages to be developed rapidly, enabling focus on the structure of the page while putting the content on Contentful, which reduces the time to make the page live.

Pages that previously took around a week to launch now take two to three days less, depending on the page size and complexity.

Contentful has allowed the team's work overhead to be saved, as previously there was back and forth for multiple changes requiring code deployment multiple times to see those changes. By using Contentful, content can be changed directly and seen updated on the live website, which saves around 30% of the time that would have been spent.

One thing that could be enhanced is the UI since it is currently only available in light mode and does not have a dark mode.

No issues have been found with the performance of Contentful, and many integrations have not been used with it.

I have used Contentful for around two plus years.

Contentful is very stable.

Scalability is not an issue as Contentful auto-scales and no issues have been faced regarding its scalability.

Customer support is fantastic.

Other options such as Sanity and Brightspot were evaluated.

Contentful receives a rating of nine out of ten because there is always room for improvement, and one improvement was suggested, so in my opinion, nine is a very good rating.

The advice to give is to go through the material provided on Contentful's platform and their learning platform as well, because doing so will make Contentful's platform more cohesive, which will help to get up to speed with the product. My overall review rating for Contentful is nine out of ten.

My main use case for Contentful is to set up content for content tools and entries for my clients as I create website pages using Contentful. I developed a custom page where clients can easily create pages from Contentful itself.

I am currently developing a website using Contentful that can be dynamic, specifically focusing on how I use content types for my clients.

The best features Contentful offers are easy data management, separate environments for different stages such as QA, UAT, production, and staging, and the ability to create dynamic pages using content.

Contentful has positively impacted my organization by making things easier. I am able to create new pages immediately without significant additional development effort.

Contentful has helped my organization in specific ways. Changing data has become much easier, so I do not have to deploy every time data changes in my application. If clients need more pages, I can build them immediately without any development work.

Contentful could be improved in the following ways. It would be much easier if I could move data from one environment to another without any CLI tools. An option to move data from one environment to another would be beneficial, so I do not have to move data manually.

I have been using Contentful for the last six months.

I would advise others looking into using Contentful that it would be a good opportunity because it significantly reduces development effort and makes it easier to manage changes. I would rate this product a 7.

Contentful is being utilized as a headless content management system so that our website and mobile applications can consume data from this CMS.

We have a website for an e-commerce platform and we are keeping all of our content related to products, user profiles, user reviews, ratings, and all website-related specific content on Contentful itself. We consume this data via the API that Contentful exposes.

Since we have multiple platforms supporting websites, native Android devices, and iOS devices, Contentful being an API-first content management system is amazing for us to integrate and utilize it across all of our platforms.

Contentful is very flexible and developer-friendly. The content modeling system allows us to structure data exactly how we need it. The API-first approach makes it great to integrate with different platforms, whether web or native devices.

The content modeling system allows us to have a specific way of segregating our data for ratings and user profiles. When we have influencers, we have a certain set of structure that we can simply edit quickly and it is reflected via the API. There is less time in terms of saving the data and having it reflected in the environment without any further builds.

The changes made in Contentful are reflected very quickly in the browser, resulting in less downtime and actually no downtime at all. There is no separate build required each time we publish new changes. We just have to make the changes in the CMS and they are quickly reflected in our environments as soon as we publish them.

Contentful has had an amazing impact on us. The customizable content models and fast, reliable APIs allow us to integrate the front end with various third-party services. It is a very customizable and scalable solution that makes Contentful stand out.

We are getting a couple of significant benefits. The first is obvious time saving. Previously, we had to run our build and review the results. Now that requirement has been completely reduced. Our content team creates and organizes content in our CMS, and any text or detail changes are really quick to adapt. We just have to publish the changes in Contentful and immediately they are available in the API being utilized by our platforms.

We have seen improvement in many areas. Our development and static content changes have been really fast. We just have to publish changes in the CMS and immediately our platforms reflect those changes without any specific build or republishing of our native applications. We have seen a significant increase in the performance of our web application. The initial load time has improved significantly because the APIs are very fast, and we are able to load our initial frame much quicker than it was earlier.

Contentful is already a very powerful and amazing tool to utilize, but sometimes the documentation and interface are a bit technical for non-developers. We have a team for content developers who create content in Contentful, and the interface makes it sometimes difficult for them to understand because it is heavy and provided with many options and segregations. This is something that could be improved.

Initially, other CMS options like Strapi have a more user-friendly CMS interface. Though they might not be as powerful as Contentful, they have clear segregation in terms of how a new user or someone from content without much CMS experience can onboard more easily. The interface and the side of options on the initial dashboard could have been improved.

For us, one of the challenges is that for non-developers, we have had to, as a developer, guide them a little or they have had to reach out to the services team to understand where and what to add. This initial onboarding could have been improved. Apart from that, the price is a bit high when we are storing more content in the CMS. When it takes more space, it becomes a little pricey.

I have been using Contentful for the last four years.

Contentful is very stable. Its APIs have 99.99% availability. There is no downtime in the new content replacement or publishing, so it is very scalable, maintainable, and highly secure.

Scalability is amazing. With the increased content load, we did not see any increase in the timing for the API response. It still remains the same. That is how scalable and configurable it is, making it an amazing tool.

The customer support is amazing. The initial demos that were given and the initial setup that our team had to do received amazing support from both the customer service team and the technical support team. They provided us with the required information and details and helped guide us through how to initially set up everything for all of our platforms.

Previously, we were utilizing AEM, which is a page-based system. It was a bit difficult in terms of training people and in terms of the flexibility they had for providing content. When it comes to Contentful, being an API-based approach, it seems much easier for developers to integrate and visualize how the data would come in JSON form and all. This is amazing.

It is on private cloud.

We are currently utilizing Amazon Web Services, which is AWS, and we did purchase Contentful from the marketplace.

Contentful is already a great tool and amazing to utilize, so there is no specific improvement I would suggest in that regard.

Pricing for the base usage is very minimal, so it is very great to adopt. However, as soon as content volume increases, since we are a huge e-commerce platform, the pricing for larger content storage is more. I would say that with higher enterprise-level scale, it becomes a little pricey. In terms of acquiring the licenses, the team has been very supportive. The initial demo that was given by the team was really great to understand the tool and how powerful it is.

We have utilized and purchased the license for Contentful and we are utilizing the product.

We evaluated Strapi as an alternative. Comparing both tools, we found Contentful to be more precise to our use case and the functionality we wanted, so we went ahead with Contentful.

Contentful is one of the best CMS options out there, being API-first and very suited for developers. They can easily set it up. Any level of organization, whether enterprises or startups, can simply utilize this tool. It is a highly digital product, so they can have control over content delivery across multiple platforms. Any organization of any size or strength could try this tool and benefit from it. Contentful is a great tool and a powerful solution to support multiple platforms, and I would rate this product a 9 out of 10.