Contentstack Adaptive Digital Experience Platform
Content workflows have become faster and teams manage dynamic multilingual pages independently
What is our primary use case?
My main use case for Contentstack is in a website where I want dynamic content, such as websites based on text and images. Dynamic, multi-language content is also required in a website, along with fast content delivery for SEO purposes, and many other use cases where I will use Contentstack in websites.
In a previous project, I used Contentstack where the client wanted all the content of the site, including all text, headings, images, and videos to be dynamic without requiring any technical developers. We used Contentstack to create all the pages and components dynamically. Everything, including background images, content, and videos, was made dynamic so that if a client wants to update it, they can directly go to the Contentstack dashboard, update there, and it automatically applies on the live site within seconds. Our website supports multi-language options where the same page and components can have content managed language-wise in the Contentstack dashboard.
Overall, Contentstack works well for managing and delivering content. I mainly use it to keep content separate from the front end, which makes updates easier and helps the development team work effectively. It allows us to manage our website content in one place, making it easy for our team to create, update, and publish pages quickly. We also appreciate that we can reuse the same content across different pages and channels, which makes it more organized.
What is most valuable?
Contentstack offers great features including various content types, entries, and assets, the ability to create reusable components, multi-language support, flexible content modeling, a good API, SDK support, use in websites or applications, excellent customer support, an easy editor, and overall ease of use for non-technical users.
Our most used feature is Content Type and Entries because it stands out, allowing us to set up a structure once and then reuse it for many pages, where our content team just fills in the fields and publishes without needing any coding. This keeps everything consistent and saves us a lot of time.
Contentstack has positively impacted our organization by making our work much faster. Our content team can now update and publish pages independently without waiting for the developer, which frees up our developers to focus on bigger tasks. This ensures that our content is more consistent across the site and allows us to launch new pages much quicker than before while also being SEO friendly.
What needs improvement?
While Contentstack has great features, it is a bit expensive, and there is a learning curve involved for complex content models. Some UI features feel limited, which are some cons of Contentstack.
Contentstack can be improved in several ways. I would like to see a more intuitive UI, better documentation for advanced use cases, and easier debugging for API or content delivery issues. Additionally, optimizing pricing and simplifying live preview setups requiring developer efforts would be beneficial.
Regarding needed improvements, while the pricing is high, especially for smaller teams, simplifying live preview setup requiring some developer efforts would be great. There is a bit of a learning curve for new users when content models get complex, so better guides or templates for beginners would really help.
For how long have I used the solution?
I have been using Contentstack for the last three years.
What do I think about the stability of the solution?
Contentstack is stable.
What do I think about the scalability of the solution?
The scalability of Contentstack is really good. As our content and traffic grow, we do not face any performance issues, and it is easy to add new pages and languages even before the website becomes large scale.
How are customer service and support?
Customer support with Contentstack is really good. I would rate customer support a nine.
Which solution did I use previously and why did I switch?
Before Contentstack, we used WordPress because it was becoming hard to manage as we grew, requiring many plugins and maintenance. It was inflexible in using content across different channels. Contentstack provided us with faster, more modern, headless setups that are easier for both our content team and developers.
What was our ROI?
We have seen a return on investment from using Contentstack, mainly through time saved on content updates. Our developers do not need to handle every small content change, reducing development efforts and helping the team move faster, though we do not have a specific ROI percentage at this time.
Which other solutions did I evaluate?
We evaluated a few options before choosing Contentstack, mainly Contentful and Strapi, but we chose Contentstack because it was easier for our content team to use, had a better workflow, and its multi-language feature was a significant advantage. Furthermore, the support team was really good.
What other advice do I have?
My advice to others looking into using Contentstack is to plan your content structure well before you start. Spend time designing your content types properly so that everything is easier later. Involve both your developers and content team early to ensure the setup works well for everyone, and utilize the support team as they are really helpful during the onboarding process.
Overall, we are really happy with Contentstack as it has made our content work faster, easier, and more organized. I would rate this product an eight.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Bulk product updates have streamlined campaign pages but user interface still needs improvement
What is our primary use case?
My main use case for Contentstack is updating POP and PDP and landing pages. Recently, the last work I did was add a dynamic pricing code to the product display page, so I go into already created pages, add the code, and push staging and live. We also create campaign pages, which are like landing pages, and add components. We have built-in components that we can customize as well.
What is most valuable?
The best features Contentstack offers are the ability to update many products at the same time, the release tool, and the scheduler. By setting promotion banners or cards, for example, for the weekends, we can just set it up, and it will go live and end at a certain time that we want.
Contentstack has positively impacted my organization because we can work with massive product SKUs, and we can now quickly use or reuse components, add products, and do bulk updates.
What needs improvement?
I think Contentstack can be improved with a more appealing user design because it seems too bland.
For how long have I used the solution?
I have been using Contentstack for two years.
What other advice do I have?
I would rate Contentstack a seven on a scale of one to ten.
I pick a seven because it is not perfect, but it does the job, and I really appreciate the reusable component and templates feature.
Regarding Contentstack's AI capabilities, I am a little worried about its governance and security, but I trust they will build a certain secure system.
Regarding Contentstack's AI capabilities, I am not sure about its accuracy and reliability of output.
I would recommend Contentstack if you are looking into using it for large scale or day-to-day seasonal promotional updates because it is very useful.
Editing website content has become smooth and support now resolves issues quickly
What is our primary use case?
My main use case for Contentstack is to update the content of websites. When working with a company that wanted to change the content of their website pages, I have changed the text, the assets, and the links.
What is most valuable?
The best feature Contentstack offers is that it is easy to use. I really appreciate the assistance part because when you get stuck with Contentstack for anything, it is easy to reach support.
What needs improvement?
Contentstack can be improved, but I do not see anything that needs improvement because it is already a good CMS.
For how long have I used the solution?
I have been using Contentstack for almost two years.
What other advice do I have?
On a scale of one to ten, I rate Contentstack overall a nine. I chose nine out of ten because it is a good CMS. Regarding Contentstack's AI capabilities, I have no opinion on its governance and security. I did not use the AI capabilities of Contentstack. Contentstack is deployed in my organization on-premises. My advice for others looking into using Contentstack would be that they can use the assistance if they get stuck with it, and otherwise I do not have any advice because it is very easy to use. My overall review rating for Contentstack is nine out of ten.
Unified content model has streamlined multi-country localization for omnichannel experiences
What is our primary use case?
My main use case for Contentstack is as a CMS, which manages omnichannel content delivery. This included a mobile application and a website which are managed in one place.
This was for a multi-country perfume and cosmetics retailer located in the Middle East.
What is most valuable?
The best features Contentstack offers are its localization and management of multi-country, multi-language, multi-purpose applications. In my example, it was a mobile application and a website which had two languages, Arabic and English. Each country had specific requirements and there were thousands of labels and different small content entries which are managed in a single place.
Contentstack's localization features helped my team manage all those languages and country specifics by grouping them in bulk content entries which helped local teams to put proper translations. As developers, we were handling only the internal application labels and then we left the content team to manage all of those localizations to make sure it fits the screen, to make sure it's translated properly, and the localization is clear and understood by local customers.
Contentstack has impacted my organization positively by helping us to deliver an application with a very good quality in terms of how it looks and feels. For our client, it was very important to have good ratings in the App Store and the results were impressive. I mean, we spent a lot of time polishing the application, making sure that all translations, and Arabic is right to left, fit the screen, it's clear, it's simple, and it's understood by people. There were multiple variations which were tested by a first cohort of users. This is about building a very well tested product.
What needs improvement?
The documentation was easy to read, but it was hard to find a specific article. When we were searching for a specific capability, I didn't know how to start the search or where the starting point was. I do believe some AI tools in documentation would be helpful.
I've seen many other CMS tools such as SAP Commerce built-in CMS, which is called SmartEdit. Contentstack is much more complex and advanced technology. I think there are still some UI improvements which can be done to simplify the work. I can give an example of Contentful, which is a little bit more user-friendly from a UI perspective. However, this is a solid product.
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
We didn't have a lot of customers, so we never faced any scalability issues. However, talking about the dev environment and then switching to prod, it was good enough. I mean, we had five to ten users of the dev environment and then we were able to switch to the production environment which had 10,000 daily average users. It's an inaccurate evaluation. I would rather say it's a top-level evaluation. The organization never had millions of users.
How are customer service and support?
Which solution did I use previously and why did I switch?
The previous CMS system was something which was tightly integrated. I don't remember the name, but it wasn't headless and it was not very enterprise grade. It was probably PHP based, web based, and completely outdated. By the time of the project, we clearly saw that we needed something more powerful.
How was the initial setup?
Contentstack is deployed in my organization as a public cloud installation. We paid for multiple environments. One of those was used only for dev purposes, the other one was QA1 and the production.
What was our ROI?
I can say that the content management routine was decreased by 30 percent in time. That was one of the metrics from the content authors we heard. The other metrics which are app rating are more related to the application itself rather than Contentstack. However, I do believe that Contentstack contributed to this high rating of the application.
Which other solutions did I evaluate?
What other advice do I have?
The best advice I would give to others looking into using Contentstack is to install a demo environment and to play with it yourself. Another recommendation is to go through documentation and see the videos because they are simple and easy to understand. I think a certification, the simple one, which is Contentstack Associate or Contentstack Basic User, will really help a person to understand the product, its concepts, its data model, content model, and how those capabilities can be used. I would rate this product a 9 out of 10.