Contentstack Adaptive Digital Experience Platform

Our main use case for Contentstack  is currently building another real estate management platform. We want to put a module out of Contentstack  for other companies to utilize the CMS, utilize aspects of personalization, and other aspects to quickly roll out their websites, as well as some of their use cases that they want to deliver, which can be customized UI and so on. We are building our basic portfolio, Swamivara LLP, and we are building an app for them. I will be able to share the link as well.

We are now building an entire listing platform using Contentstack CMS. We are also working towards another aspect called personalization. We are utilizing our social footprint of our customers to show them the right set of properties. For example, if somebody logs in from Bangalore, they should only see Bangalore properties rather than seeing the Mumbai properties or the Goa properties. We are building more categories, the price, and we are also looking at how good their purchase power parity is over a course of time and personalizing that experience. We are looking forward to using the CMS for personalization through Contentstack.

Our main use case is basically to give accessibility for any new customer who wants to log in using Contentstack and build an entire use case around it. For now, we are building a service-based model using Contentstack because I felt this is much more useful. There is a little bit of a discrepancy in the pricing model of Contentstack on how CMS, Personalize, and other products will be used. We are working on that.

Currently, we are looking forward to reselling Contentstack.

I have been using Contentstack for around twelve months. I have been working in my current field for around seven years.

Contentstack's CMS helps me for adding more properties, which is absolutely fine. Personalization helps me in terms of getting the geological footprints and other sorts of personalization parameters that I can retrieve from the browser and start giving a personalized experience. For example, if someone needs a property which is in Mumbai and wants a property in Punjab, we still cater to the needs of the audience based on the geotags. There are a lot of events that we are considering right now and building on it.

Contentstack has impacted my organization positively by having very less chaos in terms of integration with Next.js and other sorts of tools and technologies. We are now figuring out how we can leverage this technology even further for multiple use cases, such as if somebody is on Shopify , how can we use that. We are exploring through app.contentstack.com. We are not exploring through a specific use case, but we will figure it out in the future. Contentstack has created an impact of quick access to a non-tech person to add the properties right away and to work on their own personalized marketing campaigns and other aspects. It has really helped us for sure.

I would suggest increasing the developer-friendly documentation rather than just having a great product. The documentation is not developer-friendly, and the content is not so vivid and it is not made specific for the developers. There is an initial lot of handholding required. We are more worried about the pricing.

For example, somebody who is a tech person trying to integrate based on the events finds it a little bit more not so accessible. It is not so accessible for a person who is doing it for the first time. I gave it to my intern and it just took him a lot more time than it took an experienced engineer. Probably the flow has not been right in terms of the documentation to cater to multiple developers. I would suggest increasing the absolute flow of the documentation which caters to the developers first because we first use this tool rather than the marketers using it. For a marketer, there should be quick access to the quick links. I think the access to the links and the generation of the links based on the events and other aspects requires documentation and support.

Contentstack can be improved by enhancing developer documentation. Some support is needed in terms of integration, with iframes being rightly available on the portal rather than a developer going and figuring it out through the tokens and other aspects. Another thing is a code snippet directly available on app.contentstack.com rather than a developer creating it through VS Code. The integration flow is something where they have missed out.

The sign-up flow needs improvement as well.

I have been using Contentstack for around twelve months.

Contentstack is stable.

Contentstack's scalability is good.

Customer support for Contentstack is good.

We did not use any previous solutions, but we used to deliver a lot of static websites.

There is no specific detail available right now regarding pricing, setup costs, and licensing. We are also a little confused about this, and I have a customer who is ready to adopt, but he is a little skeptical because of only one reason. He does not understand the pricing of Contentstack.

We need fewer employees for sure.

Before choosing Contentstack, I evaluated other options such as WordPress and Adobe Experience Manager , which is very costly. We also use other sorts of CMS tools. We were fond of Contentstack's personalization for sure. Strapi  is something that we also evaluated.

Contentstack has impacted my organization positively by having very less chaos in terms of integration with Next.js and other sorts of tools and technologies. We are now figuring out how we can leverage this technology even further for multiple use cases, such as if somebody is on Shopify , how can we use that. We are exploring through app.contentstack.com, though we are not exploring through a specific use case. We will figure it out in the future. Contentstack has created an impact of quick access for a non-tech person to add the properties right away and to work on their own personalized marketing campaigns and other aspects. It has really helped us for sure. My overall review rating for Contentstack is eight out of ten.

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.

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.

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.

I have been using Contentstack for the last one and a half years.

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.