I have been using Contentstack for six or seven months within my current company.
Basically, earlier we had a brand website on WordPress, and we have been using Contentstack as a CMS where we have integrated the CMS by using their APIs into our Next.js application.
For example, we had a blog post on WordPress. What we did was create a content type on Contentstack with a few custom fields. Then we migrated all the content from WordPress to Contentstack via a migration script, which is a custom script. Then we are utilizing the Contentstack APIs and management APIs to fetch all that data to display it in our front-end Next.js application.
We are using Contentstack as a CMS platform, and we are also exploring and developing custom apps to integrate on Contentstack.
The SDK is really quick compared to others, and we have more flexibility to organize our CMS structure on the backend. We can group all the types based on a particular label, which is helpful. Contentstack has an inbuilt webhook implementation and a very straightforward, quick-to-understand dashboard. Additionally, we have role-based access, which is really valuable when working with a good team.
The speed index has had a great impact. Earlier we had something in the 60s on Google Page Insights, but now we are able to achieve 90-plus. We also have more optimized performance on the Core Web Vitals, which is needed for SEO or if we are running Google Ads.
I will not give full credit to Contentstack, but we had great results on optimized performance that eventually impacted our SEO. We are getting good results there. It is a combination of Contentstack and Next.js, but the API responses that we are fetching from Contentstack are really quick, and we have an option to optimize the queries based on what we want as a response.
I majorly work on structuring the CMS on the backend. I feel that we have restrictions on fields. On the backend, we have conditional logic as well. We can display a specific field based on a specific condition, but I feel it is too restricted. We cannot use it with global fields or a modular field. That is something the Contentstack team can address and remove those restrictions.
Additionally, two or three months back, I connected with the support team of Contentstack. In the URL field, if we want to add any validation, we do not have that option at the code level or on the backend CMS. We can look at that. We have that field for one default URL, but we should keep that field universally if we want to add a regex-based validation.
Some of the restrictions that we really do not want could be optimized further. There are also fewer field options to add. We have JSON RTE, but we should have a raw JSON field as well.
I have been using Contentstack for six or seven months within my current company.
Considering some of the improvements, Contentstack will be great. Otherwise, it is capable and stable enough to implement if anyone is looking for it.
Customer support is really good and quick. However, any feature request or any new request takes longer than expected.
We used WordPress, as I already mentioned. WordPress is a CMS. We switched because we were restricted from optimizing a few things because of WordPress's core files. There were also some security downsides with WordPress.
