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.

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.

My main use case for Contentful is for authoring purposes, such as storing data and retrieving data from Contentful by using Contentful APIs and managing content.

A specific example of how I use Contentful for authoring or managing content is that I integrate APIs. There are many APIs available for managing content. First, I integrate Contentful in our code and from there, by using their APIs, I retrieve the content from Contentful. In Contentful, there are fields and models in which I create some models and some fields for storing content. I make fields and models in a way so that they can be reusable for other projects and components as well. This is how I'm using it and it is very useful.

Contentful is very easy to learn because the beneficial aspect I discovered is that we are able to use reusable components. If we make one component, we can use it for another component as well. The integration part is very easy, and anyone who wants to learn Contentful can learn it in a few months. It is very useful. There are features such as Rich Text, which handles data formatting so we don't have to work from our code. This is the best feature I have experienced, the Rich Text.

The best features Contentful offers in my opinion are the models, the fields, and the Rich Text. We can manage content according to the UI—whatever the UI is, we can manage that content in Contentful accordingly. This is the best feature I have found. It literally reduces the code, so a coder doesn't need to think about content, where to hold it and where not to hold it.

These features help my team's workflow. For example, if I have five to six components in my projects and there are limitations of 50 models we can create, we can use those 50 models in our project, and anyone can use that.

Contentful has impacted my organization positively because it is the best headless CMS, and it is very useful for my organization. Content management is very easy with it. When we started using Contentful, we stopped worrying about the content, where to place it and how to manage it, how to design it, or how to show it in the front-end. These things are managed by Contentful, which has impacted our organization very positively.

Since using Contentful, it has saved a lot of time for our team. We don't need to put content in our code and make the project heavy. We use the content in Contentful, integrate those APIs, and get the content from there. We are using it in every project; Contentful is very useful.

I think there are small things that can be improved in Contentful. Some things are very complex. When we are using Rich Text, we need to integrate that. It is not very easy to understand the Rich Text part, but it is very useful in that sense.

The most important area for improvement is the documentation and exam pattern. When I go through the documentation, I get a video for every topic, but there are many complex things which I am not able to understand because they give only one chance to pass the exam. I think there should be two attempts for passing the exam; it is very difficult to pass that exam in one attempt. I faced that issue, so work on the documentation and the exam pattern, allowing at least two attempts.

I have been using Contentful for two years.

In my experience, Contentful is stable.

Contentful's scalability in my projects is very much scalable.

The customer support for Contentful is very good.

I previously used Sanity before Contentful. We could make models and schemas in our code, which would then be reflected on the browsers, allowing us to manage it accordingly for any of the projects.

I think Contentful is the best option to use and I did not evaluate any other options before choosing Contentful.

I have seen a return on investment with fewer employees needed and time saved, but the money costs are quite high.

The pricing, setup cost, and licensing for Contentful are very high.

I rate Contentful an eight out of ten. Eight is a good number.

I chose eight out of ten because some things are very complex in Contentful. We cannot manage content according to some functionalities. If I compare it with other content management tools available in the market, I rated it an eight because some are very easy to access, very easy to learn, and very easy to manage in some parts.

My advice for others looking into using Contentful is that if you are ready to invest money and want a quality tool where you can manage your content very precisely, then go for it; it is very good to use. My overall rating for Contentful is eight out of ten.

My main use case for Contentful in that recent project is image content management, including image content and descriptions that we are not getting from our server. Examples include launch screens, dynamic banners, and product images. Some product images we are getting from Contentful.

I will give you an example of how I used Contentful for managing those images and banners in my project. I am working on a kiosk and mobile application. For the kiosk use case, we have a launch screen where we are showing a few banners, and the banner is totally based on the store. For instance, there is a store X where I need to play a promotional banner for a tendy at 4.9 dollars, and there is a store Y where I want to promote a tendy with 3.9 dollars. In that scenario, I use it in the kiosk. For the mobile application, I use it extensively. We integrated a loyalty platform, and for all the loyalty information, we are fetching from Contentful. We are configuring the loyalty data from Contentful and retrieving it. Also, for some product images, we are using Contentful.

These are the major use cases which I am using.

The best features Contentful offers in my experience are the management of the content. I can configure my content based on the store, time zone, and time frame. I can configure my data on a specific store and a default store. I can have the last updated data. This makes it too easy for me to manage my dynamic content.

When I talk about configuring content by store and time frame, that flexibility helps my team and my workflow. For example, I want to play a promotion in my kiosk only from 10 AM to 7 PM. After that, I want to play a different promotion. I would just configure it with the help of Contentful. I will use the time slot or time frame where I will show a promotional banner, X banner, from 10 to 7. After 10 to 7, I will show the default banner.

Contentful has positively impacted my organization as it upscales the revenue and enhances my mobile and kiosk application appearance and feel with dynamic content. We have integrated it for the loyalty as well. So it helps us to retain our customers with the dynamic content of the loyalty and dynamic promotion from the loyalty, which we are configuring into Contentful. Also, for promotion purposes, we are using Contentful, so it is totally worth it.

As far as I use Contentful, it is totally fine. There is no improvement for now. As I am using it for only six to eight months, I am not the correct person to judge or prejudge Contentful. I want to explore more as I am an active user of Contentful.

I am using Contentful for the last seven to eight months in one of my recent projects.

Contentful is stable in my experience, and I find it totally stable.

In terms of the scalability part of Contentful, it is totally fine, and I have not faced any challenges in my past experience.

My experience with customer support is that I have not reached out to them. It has been working fine, so I have not needed it yet.

In the initial stage of the product I am working on, we chose Contentful, so we have not explored anything else.

Before choosing Contentful, we did not evaluate other options, as we have not explored any other tool.

I have seen a return on investment, and I can share relevant metrics in terms of money saved and time saved. It saved money and resource time. If I were implementing dynamic content management in-house, it would take a lot of effort to implement and then integrate. Contentful is a platform where I can just get the license and start working on that. So it is quite easy, and with its help, we are able to get the data from Contentful. Obviously, if we are using Contentful, we just need to configure our data with no worry about how Contentful manages our dynamic data.

I am not the right person to answer this question as we have our separate team who finalizes it. There is a finance team who takes all the decisions regarding costing and everything. I am on the tech side, so I can help with the technical part.

I have seen a return on investment, and I can share relevant metrics in terms of money saved and time saved. It saved money and resource time. If I were implementing dynamic content management in-house, it would take a lot of effort to implement and then integrate. Contentful is a platform where I can just get the license and start working on that. So it is quite easy, and with its help, we are able to get the data from Contentful. Obviously, if we are using Contentful, we just need to configure our data with no worry about how Contentful manages our dynamic data.

I am not the right person to answer this question as we have our separate team who finalizes it. There is a finance team who takes all the decisions regarding costing and everything. I am on the tech side, so I can help with the technical part.

In the initial stage of the product I am working on, we chose Contentful, so we have not explored anything else.

Before choosing Contentful, we did not evaluate other options, as we have not explored any other tool.

All the features I use, I have explained to you, and I am pretty much in love with Contentful. I would rate Contentful a nine out of ten. I am in the exploring phase, that is why I am deducting one point.

I choose a nine for Contentful because of its performance, and it is bug-free and easy to implement. Contentful is easy to integrate. With the help of GraphQL, we can easily handle my Contentful data. That is why I gave a nine.

My advice to others looking into using Contentful is that if you have a use case where you need to dynamically manage the content, then you should definitely go with Contentful. Contentful has a very stable product and is bug-free. First of all, it is bug-free and easy to configure. Anyone from the team can easily configure our Contentful. I am giving this review a rating of nine out of ten.

My main use case for Contentful is that our company's website is built on Contentful, so I use it for updating content, creating new templates, pages, publishing them, and conducting A/B testing and various marketing activities.

A specific example of something I recently did with Contentful is that I created a new page called Press Release on my company's website two days ago, where I uploaded the teaser image, banner image, the content, and the written by author profile.

Regarding my main use case and recent activities with Contentful, our company has done many innovations for our clients' websites, including migrating from another platform to Contentful with around 40 to 50 plus websites, and we are consistently using the headless version, which makes it very easy to update and check the content.

In my opinion, the best feature that Contentful offers is the headless capability.

The headless feature stands out for me because it is very helpful for our team, especially for anyone who is non-technical when they update the content or create new pages. Using the template features allows them to easily update the content and modify it. The nested hierarchy plays a key role here since you do not have to change one component repeatedly across several pages; you just have to make the change in one component, and it will automatically propagate wherever it is nested.

I think this is more than sufficient regarding the features in today's era for both technical and non-technical people.

Contentful has positively impacted my organization because, as I mentioned, since we are using the headless setup, when we need to create new pages, update content, or conduct any marketing activity, we no longer need to rely on a technical person. Our marketing or SEO team can simply perform these tasks.

This change has resulted in measurable outcomes, including an increase in sessions on our website.

Contentful can improve by addressing one technical issue regarding the creation of builds. When we give access, there is no access hierarchy, so if we give an author access, they can also create a build, which sometimes leads to a situation where an author who is only supposed to update or upload content might mistakenly click the build button, and the content goes live without testing or checking. Contentful can create an access level hierarchy to ensure that authors can only create and update content but not push it live.

Apart from the access hierarchy improvement, everything else is excellent.

I have been using Contentful for the last 2.5 years.

Contentful is stable for my organization.

Contentful's scalability meets our needs according to our requirements.

I have not used customer support because we do not face any challenges, but I can say that if transitions are very smooth, then the customer support is very supportive.

We started using Contentful only for our website and did not previously use a different solution.

The initial setup and onboarding process with Contentful for my team was not very difficult. There were a few challenges that the lead developer handled, but there were no major challenges.

Initially, we followed the documentation and training resources provided by Contentful, which were very helpful. As we started implementing it and doing hands-on work, everything became very easy. Initially, it was very helpful; however, now we do not rely on documentation unless there is a major issue.

I have seen a return on investment because now, to handle our website, we do not need technical staff. The marketing team can manage content operations, A/B testing, and marketing tasks themselves, requiring the technical team only for template-based or page structure changes. This means our team size and costs are reduced.

My experience with Contentful regarding pricing, setup cost, and licensing is that it is acceptable.

Before choosing Contentful, we evaluated AEM but found its pricing to be very high.

My advice to others looking into using Contentful is that if you want headless capabilities, budget-friendly pricing, and a smaller team, then Contentful is the option.

I do not have any additional thoughts about Contentful, but I would like to emphasize that they should look into the access hierarchy part for improvements; apart from this, everything is excellent. I gave Contentful a rating of 9 out of 10.

My main use case for Contentful is building websites and managing the content. We have a public facing website where we showcase our products and offerings to people, and all of that content, images, and everything is managed through Contentful.

The best features Contentful offers include the Rich Text editor, the linking, the images, pages, and templates. I rely heavily on the Rich Text editor because that is where I create customized components. For example, Rich Text lets us paste images and links, and based on the JSON response structure we receive from Contentful with the GraphQL query, we know the structure of it, which helps render specific components on the screen, such as a banner that will have background images, buttons, and text, and the same goes for the slider and carousel.

Contentful has impacted my organization positively because the business is able to change the content without the help of a developer, and they can make a deployment very easily. This has led to measurable outcomes, such as a faster time-to-market and reduced workload for developers.

I think Contentful can be improved in several ways. Sometimes the linking is challenging. If you are using too many links, then it is actually making the application deployment time longer, so Contentful needs to figure out a way to solve that problem. Additionally, cost-wise, I feel our organization thinks it is too much because we were planning to use Contentful for our global site, which has four languages support, and for each language, we need to create different spaces. If Contentful could allow us to add the four languages in one go, that would be great.

I have been using Contentful for the last two years.

Contentful is stable.

Contentful's scalability is good.

The customer support for Contentful is good.

Previously, we used an on-premise based Content Management System, which was Adobe AEM, and we changed to Contentful because of faster deployment and evolving technologies.

I would say we have seen a return on investment because the cost in the infrastructure got saved. Contentful is a platform offering that manages the infrastructure for us, resulting in savings in terms of infrastructure.

My experience with pricing, setup cost, and licensing is that mostly, a developer will not be managing those aspects, but from my point of view, Contentful is a bit pricey.

I rate Contentful an eight on a scale of one to ten. My advice for others looking into using Contentful is to go for it. I have no additional thoughts about Contentful before we wrap up. My overall rating for this review is eight.

My main use case for Contentful is for migrating our Oracle ATG server into Contentful as a migration project.

During that migration project, we created multiple content types and developed a custom app where we map the ATG server code to our content types. We used that mapping to import the particular content to Contentful.

After the migration, we used this particular content for the website, specifically for our client Sephora, where we utilized all this content.

Contentful offers many best features including Preview, Custom Apps, migrations, Merge App, and workflows.

We used the preview feature whenever we wanted to see how particular content looks, and at that time we ran our server locally and tested it. Additionally, we used custom apps for building bulk editors and multiple features where we could reuse some of the code.

Contentful has positively impacted my organization as it has been a major breakthrough. The producers can automatically update their content without relying on developers, which is really helpful for the producers.

I could say we saved around 60% of the time for developers. Previously, we maintained all the content, but now producers handle that, which allows developers and producers to publish their content immediately when they want to update it.

Contentful needs to be improved for migration, not only for migration, but from lower to higher environments as well, as the schema diffs and everything are not working as expected. Improving the CI/CD pipelines would be greatly helpful, and it could build similar capabilities to Builder.io for enhanced growth when using Contentful.

I have been using Contentful for more than five years.

Contentful is stable.

Contentful is scalable. We can scale the application to any level we want without any problems regarding scalability.

Customer support is good. There are three levels of support available, and level one support resolves issues within 15 minutes to one hour.

We previously used ATG Oracle Cloud, which is too old and requires developers to handle the cloud architecture and content, leading to our migration to Contentful.

I have seen a return on investment. Previously, we used to have 10 developers for the ATG Oracle cloud, but for Contentful, we only need two developers, and once it is streamlined, producers can handle everything without the need for developers.

I evaluated Strapi, but Strapi requires everything to be done by the developer only, including in-house premises and deployments, while Contentful allows us to do everything on the fly.

Others looking into using Contentful can use it seamlessly without relying on any other deployments. Everything is present in Contentful itself, and any custom apps can also be deployed within Contentful without needing separate servers.