I would prefer a model where template changes are stored locally in the browser or somewhere as an incomplete draft. If there is an explicit save or create draft action, that would make it easier without every small change becoming part of the entry's change history. Whenever we accidentally change some value or if we are experimenting with the editor interface by changing and modifying the existing content, that will already become the draft. This is an improvement that Contentful could make. Users can change content and choose to save only when they want to. The most annoying feature that I have experienced is that when we are editing the content, it is automatically saved, no matter what. I prefer it in that it helps in not losing data when you are disconnected or the system has crashed or something has happened, but it is saving as the draft. Instead of that, I would prefer to save the edited content to the local browser's cache specific to that user. When the user wants to save it manually, they can press a save or save-to-draft button, so that it will be saved as a draft and be available to all other people. They can see it, and it can be added to the change history after clicking manually. Currently, it is just saving automatically, which is quite annoying. Sometimes, even if you revert your changes, it still says something has changed. I prefer manual buttons to save the changes and have a cache at the browser level.
While Contentful already incorporates a lot of AI integration, improvements could be made in feature-wise AI integrations, such as generating SEO data for product catalogs or assisting marketers in writing new articles, which would make it more future-ready. The interface and workflows of Contentful are already intuitive and user-friendly, so I do not see any major improvements needed in those areas, as they work well as they are. Contentful is good as it is, with no further improvements needed in terms of integrations or performance.
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.
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.
Senior Front Full Stack Engineer & End Ai Architect & Engineer at Immediate Tiger - IT
Real User
Top 5
Mar 22, 2026
To be honest, I don't work so deeply with Contentful to see anything that I would change. Based on what I do, everything is really done in the sense that I don't need any changes. Maybe in the future something will change, but at this specific moment, I think I got everything I need from Contentful. The only thing I would mention is basically fields and types. That's what I found quite difficult at the beginning to understand how all that works. So there is some space to improve. Apart from that, I didn't have really any big requirements in terms of any changes. I would need to look very deeply once again at what I did because I did that some time ago. For now, I don't need any updates from Contentful. At least, I don't see it at this specific moment. The job I really do by using Contentful is really little. I don't post every week or every single day to basically expect something more in terms of quality. I just noticed that there's a new AI Automation tab. I have not seen that before. At this specific moment, I think everything works in a really great way. It's very stable. That's the most important when you post content. The last thing you want to see is that the service disappears or your content is somehow changed. For me, it's been very stable. Even though I have just four articles, they're very important for me, and my personal brand is very important for me as well. I just try to make sure that I stick to basically stable solutions. For one year and six months, I never had any problems with Contentful. Even when I was updating the module, I never had any problems.
Frontend Developer at a consultancy with 11-50 employees
Real User
Top 5
Mar 21, 2026
One area where I believe Contentful can be improved is better handling of complex content relationships, as when content is deeply nested with references inside references, the queries can get messy and hard to manage on the front end. A more intuitive way to visualize and manage relationships, with built-in tools to simplify nested data handling, would be beneficial. Another improvement could be performance with large data sets, as with many entries, API responses can slow down and pagination can become tricky; better query optimizations and smarter caching tools built-in could help. Lastly, content modeling can get complex since designing models requires experience, and it is easy to over-complicate; better templates and guided modeling with suggestions based on use cases, such as e-commerce or blog, could improve usability.
Deployments could be somewhat easier for migrating content from lower environments to higher environments, which is a challenge we are currently experiencing with Contentful.
I believe Contentful could be improved by adding a way to migrate data between spaces, such as from a staging space to production, and the support team could respond to questions much faster with an increased response time. We have run into some limitations in adding too many content models, and I note that the next pricing tier is substantially more expensive. I cannot say we've experienced any negative return on investment impacts from using Contentful.
I believe it would be nice to have some documentation, especially for new learners who are starting. A minor issue I have is that Contentful does not have a way to organize fields within an entry. I think there needs to be a UI to filter entries for Contentful.
Contentful could be improved on documentation for adoption to the platform and to enhance content migration between traditional platforms to Contentful. It would be beneficial if there were a way to migrate data between spaces, such as from staging space to production.
One improvement I believe Contentful could make is regarding licensing, as there is no way to obtain it for free over time. I would add that the user interface to filter entries needs improvement. Content type limitations can be frustrating at times. A comments dashboard is needed. Other improvements needed for Contentful include improving the response time from customer support.
Contentful is a modern content management platform known for its reusable components, easy integration, and flexible content modeling. It enables content management across multiple platforms quickly and efficiently.Contentful’s API-first architecture and Rich Text editor offer seamless content management for different platforms, enhancing productivity by minimizing coding efforts and allowing non-technical individuals to update content effortlessly. It supports diverse needs like content...
I would prefer a model where template changes are stored locally in the browser or somewhere as an incomplete draft. If there is an explicit save or create draft action, that would make it easier without every small change becoming part of the entry's change history. Whenever we accidentally change some value or if we are experimenting with the editor interface by changing and modifying the existing content, that will already become the draft. This is an improvement that Contentful could make. Users can change content and choose to save only when they want to. The most annoying feature that I have experienced is that when we are editing the content, it is automatically saved, no matter what. I prefer it in that it helps in not losing data when you are disconnected or the system has crashed or something has happened, but it is saving as the draft. Instead of that, I would prefer to save the edited content to the local browser's cache specific to that user. When the user wants to save it manually, they can press a save or save-to-draft button, so that it will be saved as a draft and be available to all other people. They can see it, and it can be added to the change history after clicking manually. Currently, it is just saving automatically, which is quite annoying. Sometimes, even if you revert your changes, it still says something has changed. I prefer manual buttons to save the changes and have a cache at the browser level.
While Contentful already incorporates a lot of AI integration, improvements could be made in feature-wise AI integrations, such as generating SEO data for product catalogs or assisting marketers in writing new articles, which would make it more future-ready. The interface and workflows of Contentful are already intuitive and user-friendly, so I do not see any major improvements needed in those areas, as they work well as they are. Contentful is good as it is, with no further improvements needed in terms of integrations or performance.
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.
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.
To be honest, I don't work so deeply with Contentful to see anything that I would change. Based on what I do, everything is really done in the sense that I don't need any changes. Maybe in the future something will change, but at this specific moment, I think I got everything I need from Contentful. The only thing I would mention is basically fields and types. That's what I found quite difficult at the beginning to understand how all that works. So there is some space to improve. Apart from that, I didn't have really any big requirements in terms of any changes. I would need to look very deeply once again at what I did because I did that some time ago. For now, I don't need any updates from Contentful. At least, I don't see it at this specific moment. The job I really do by using Contentful is really little. I don't post every week or every single day to basically expect something more in terms of quality. I just noticed that there's a new AI Automation tab. I have not seen that before. At this specific moment, I think everything works in a really great way. It's very stable. That's the most important when you post content. The last thing you want to see is that the service disappears or your content is somehow changed. For me, it's been very stable. Even though I have just four articles, they're very important for me, and my personal brand is very important for me as well. I just try to make sure that I stick to basically stable solutions. For one year and six months, I never had any problems with Contentful. Even when I was updating the module, I never had any problems.
One area where I believe Contentful can be improved is better handling of complex content relationships, as when content is deeply nested with references inside references, the queries can get messy and hard to manage on the front end. A more intuitive way to visualize and manage relationships, with built-in tools to simplify nested data handling, would be beneficial. Another improvement could be performance with large data sets, as with many entries, API responses can slow down and pagination can become tricky; better query optimizations and smarter caching tools built-in could help. Lastly, content modeling can get complex since designing models requires experience, and it is easy to over-complicate; better templates and guided modeling with suggestions based on use cases, such as e-commerce or blog, could improve usability.
Deployments could be somewhat easier for migrating content from lower environments to higher environments, which is a challenge we are currently experiencing with Contentful.
I believe Contentful could be improved by adding a way to migrate data between spaces, such as from a staging space to production, and the support team could respond to questions much faster with an increased response time. We have run into some limitations in adding too many content models, and I note that the next pricing tier is substantially more expensive. I cannot say we've experienced any negative return on investment impacts from using Contentful.
I believe it would be nice to have some documentation, especially for new learners who are starting. A minor issue I have is that Contentful does not have a way to organize fields within an entry. I think there needs to be a UI to filter entries for Contentful.
Contentful could be improved on documentation for adoption to the platform and to enhance content migration between traditional platforms to Contentful. It would be beneficial if there were a way to migrate data between spaces, such as from staging space to production.
One improvement I believe Contentful could make is regarding licensing, as there is no way to obtain it for free over time. I would add that the user interface to filter entries needs improvement. Content type limitations can be frustrating at times. A comments dashboard is needed. Other improvements needed for Contentful include improving the response time from customer support.