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?
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?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.