Headless content management has streamlined page delivery and now supports rapid front-end integration
What is our primary use case?
Contentstack serves as my main solution for headless architecture, where I manage all product listing pages, product detail pages, metadata, images, navigations, and mega menus through a headless approach. I deliver all PDP, PLP, mega menu, and assets via Contentstack, where React uses it as a JSON structure and renders it on the pages.
What is most valuable?
The best feature of Contentstack is that without coding, I can deliver all headless information to React or any other front-end applications. Additionally, I can manage assets easily, the mega menu, and tagging and references. Contentstack has positively impacted my organization as it represents a long-term engagement and delivers a better headless approach compared to Adobe Experience Manager, though there are some caching issues that need to be addressed programmatically. Contentstack has saved time and improved efficiency, and compared to other products, it is cost-effective and not expensive.
What needs improvement?
For improvement, I want to clear the cache for the pages, as Contentstack does not provide a default way of invalidating the cache. I need to write hooks and webhooks to implement this functionality, while other products are more comfortable for clearing or invalidating the cache.
Another area where Contentstack could improve is digital assets management, as it is not beneficial for storing videos, large DAM assets, or digital assets. Improvement in that area would be valuable for my organization.
The main areas for improvement in Contentstack are digital assets and caching. The remaining features are functioning adequately.
For how long have I used the solution?
I have been using Contentstack for the last one and a half years.
What other advice do I have?
On a scale of one to ten, I would rate Contentstack an eight. I chose eight because most applications are moving to a headless approach, and with other products, a lot of coding and additional work is required, whereas here, within a few hours, I can publish content and provide the endpoint to the front-end application to utilize it. My advice to others looking into using Contentstack is that if your application is pure headless, do not go with other products, as Contentstack is more than enough to handle your headless content information. I would rate this product eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Content editing has become intuitive and AI tools now generate SEO titles and descriptions
What is our primary use case?
I usually useContentstack as a CMS platform to manage the data of the website and allow non-technical people to use the Contentstack admin panel to edit some parts of the website, mostly content-wise. Additionally, I have integrated some AI tools to Contentstack itself, using developer tools that enable non-technical people to generate titles, SEO tags, descriptions, parse the images they upload, and make their life easier.
What is most valuable?
The ease of use, which I mentioned as the best part, is especially highlighted by the clean UI and predictable UX of Contentstack, as there is not too much information on the screen at the same time that can confuse the users. Everything is step-by-step and cleanly placed, and as a front-end engineer, I appreciate that. For the developer experience, the documentation is fine, even though API integration can be a bit tricky, but it is usable.
Contentstack is a legitimate CMS platform that nearly offers everything that other competitors also offer, such as content modeling, entries, and stacks. Everything is legitimate and good. Contentstack also offers GraphQL API, REST API, and all types are in place. Everything works seamlessly, and it is one of the most popular CMSs out there and easy to use for non-technical persons. The ease of use is the best part of it.
What needs improvement?
There are definitely some improvements needed in the documentation part to make it easier for developers to understand. The API, specifically the Content Delivery API, can be a bit tricky sometimes. This can be improved by refactoring or making it a bit more seamless and easier to use for developers.
Overall, the documentation part and the overall API integration part can be simplified, or perhaps Contentstack can provide a step-by-step guide in the documentation or update courses to be shorter, easier to access, and allow developers to obtain new certificates.
For how long have I used the solution?
I have used Contentstack in a couple of projects, and I have even written custom AI tools that were connected to Contentstack fields which were generating using AI for image optimizations, SEO tags, title generation, and description generation.
What do I think about the stability of the solution?
Contentstack is pretty stable.
What do I think about the scalability of the solution?
The scalability of Contentstack is good, it is legitimate, and you can use it for bigger projects.
What about the implementation team?
The process of integrating those AI tools into Contentstack was not straightforward because it was our team's first time integrating such AI tools not only to Contentstack but also to Contentful and a couple more CMS models. There were some challenges, of course, but we used documentation and everything we found in online forums and somehow we made it happen. However, it was not straightforward, and there were some issues with state management and some confusing parts.
After using it for a while and getting hands dirty and knowing a bit more about how Contentstack is built and how we can interact with the fields and custom fields like theming, it became a bit easier. At the end, we developed a great product and handed it over to the client.
What other advice do I have?
My advice for others looking into using Contentstack is to pass their course for developers if you are a developer, and learn how to do things properly before getting your hands dirty. In order to make a good, scalable product and use Contentstack efficiently, you need to know how to use it beforehand. Check out their courses and documentation, and then start doing some work with them.
I would rate Contentstack an eight because I deduct one point for the documentation, one point for the API integration, and overall, other things are fine.
Smooth, Collaborative Onboarding with Responsive Support
What do you like best about the product?
Onboarding with Contentstack has been super smooth and collaborative. Any feedback or emails we share are well received and acknowledged by both the customer support team and the customer success manager, which strengthens our trust.
What do you dislike about the product?
The UI changes aren’t always appealing, but there has been a lot of improvement in this area over the last two years. That said, running into limitations around locale count setup and the number of fields allowed in a content type is a bit concerning. Publishing heavy pages with multiple references sometimes slows the system
What problems is the product solving and how is that benefiting you?
We wanted to move from two legacy systems to a modern headless CMS and migrate a huge volume of data, but it wasn’t a simple “as-is” lift-and-shift. CS architects and support assisted us to navigate the process and work through the added complexities along the way.
Intuitive and Flexible Content Management
What do you like best about the product?
I use Contentstack for managing our webpage. It helps me to manage and deliver content in a flexible and scalable way. I really like the flexibility and ease of managing content. The intuitive interface makes it easy to create or edit content without needing a lot of technical know-how, which saves time. I also appreciate how quickly the content can be published. Overall, the initial setup was very easy, and it's a better tool to manage content compared to what we used before.
What do you dislike about the product?
Some customization options or workflows could be more intuitive
What problems is the product solving and how is that benefiting you?
I use Contentstack for managing and delivering content flexibly and scalably. Its intuitive interface makes editing easy, saving time, and the quick publishing feature is invaluable. It's a better tool with more options compared to what we used before.
Streamlined Experience with Powerful CMS
What do you like best about the product?
I'm a huge fan of Contentstack. I really appreciate its headless architecture and modular approach, which allows us to integrate existing products seamlessly. It enables us to have omnichannel marketing that we've never had before. I find the interface easy to work with, and the headless CMS is great. I love the simple core of Contentstack as a content database with great publishing capabilities. It allows non-engineers to publish content and marketers to keep the site up to date. Contentstack does this core function very well, and everything else is extra.
What do you dislike about the product?
There needs to be more work with AI, but I actually think that it works pretty well for an AI workflow as is.
What problems is the product solving and how is that benefiting you?
Contentstack's headless architecture lets us integrate our existing products seamlessly, supporting omnichannel marketing. It's an easy interface and creates automation tools, allowing non-engineers to publish content and keep sites updated efficiently.
Flexible, Scalable Headless CMS with an Intuitive UI and Strong API Integrations
What do you like best about the product?
What I like best about Contentstack is its flexibility and scalability. The headless CMS approach makes it easy to manage content across multiple channels, while the user interface is intuitive and efficient for both developers and content editors. I also appreciate the strong API support and integrations, which make it easy to fit into modern workflows.
What do you dislike about the product?
One downside of Contentstack is that it can have a bit of a learning curve, especially for new users unfamiliar with headless CMS platforms. Some parts of the interface and workflows could be more intuitive. Additionally, pricing can be a concern for smaller teams, and certain advanced features may require more technical knowledge to fully utilize.
What problems is the product solving and how is that benefiting you?
Contentstack solves the problem of managing and delivering content across multiple platforms from a single source. By using a headless CMS approach, it separates content from presentation, which gives us more flexibility in how and where we publish. This benefits us by improving efficiency, enabling faster updates, and allowing our team to scale content operations without being tied to a specific frontend or technology stack.
Streamlines Content Management with Ease
What do you like best about the product?
I enjoy that Contentstack is an advanced tool. It helps to integrate all our websites in one place, making it easy to manage all of them at once. I also find it easy to copy components between them. Basically, it provides everything we need.
What do you dislike about the product?
Sometimes we need personalized solutions that are specific for our business, and I wish to have more personalized solutions that are easy to develop from your side. It would be nice to get them quicker.
What problems is the product solving and how is that benefiting you?
Contentstack helps integrate all our websites in one place and is easy to manage. We can manage all sites at once and copy components between them.
Excellent functionality, perfect for the business environment. Licensing a bit high.
What do you like best about the product?
The business-grade quality of the tool as well as the constant evolution of the product, during the 3 years of use I have seen how they develop new functionalities keeping the product up to date. The interface is quite intuitive and they have complete and accessible documentation.
What do you dislike about the product?
I have had some minor related incidents stemming from an accelerated release of new features, I would appreciate more thorough validation.
What problems is the product solving and how is that benefiting you?
Contentstack allows the integration of multidisciplinary teams in a business environment. The role and attribute definition scheme is very detailed. The version control is excellent.
Streamlined Reviews with Effortless Usability
What do you like best about the product?
I use Contentstack for reviewing help articles at work, and it allows us to have a formal review process while keeping all our articles in one place. I find it easy to use and I like being able to preview, which makes my reviews faster. The initial setup was easy enough for me.
What do you dislike about the product?
Nothing
What problems is the product solving and how is that benefiting you?
I use Contentstack for reviewing help articles at work. It provides a formal review process and centralizes our articles. It's easy to use and the preview feature speeds up my reviews.
Simple, Structured Content Management Across 25 Languages
What do you like best about the product?
The simplicity of the platform stands out. I am working with content across Europe in around 25 languages, and Contentstack keeps everything structured and easy to manage.
What do you dislike about the product?
The ‘Go back’ functionality could be improved. I work with multiple language locales and switch between them very frequently. When I click the ‘Go back’ arrow, it often takes me through the previously viewed languages instead of returning to the previous content level, such as the page template. This means it can take several clicks to get back to the original entry I was working on.
What problems is the product solving and how is that benefiting you?
Managing content across multiple languages can be tricky, but Contentstack makes it simple and efficient. It saves time, is easy to use, and publications happen quickly. It is smooth and responsive, so it doesn’t cause delays or frustration, which is a game changer.