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.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.