My main use case for Contentstack during my time using it was content management for the website of Air France.
For Air France, there was an existing website, and during the merging of the tools Tridion and TeamSite, we had to reallocate the existing content into Contentstack.
I found that the process of migration was straightforward for some aspects because the work was mainly copy and paste. We were copying and pasting the text, title text, main body text, alt text, images, and URLs from the existing content management system to Contentstack, although hosting the images required additional work.
One of the best features Contentstack offers is that when you create one item, such as a URL, you can use this item across other pages, which helps keep the content clean, although it can also lead to difficulties in finding this information for other pages.
I noticed that Contentstack positively impacted the organization because having one content management system instead of the previous two different systems for KLM and Air France became more efficient for training new people, although adjusting from TeamSite and Tridion to Contentstack was challenging.
While migrating the content, I found many quality issues rather than positive outcomes because our final goal was to recreate the same website within Contentstack. There were many times where we had to check, correct, and republish the content, which challenged the notion of a positive impact.
A particular difficulty during the migration was that if somebody changed anything by accident on the global level, everything, including every language version, got messed up, which was a problem. Identifying the source of the problem was troublesome.
I think the naming of each content stack was not clear enough to understand what was inside, making it challenging to see what is contained in each stack. This took a considerable amount of time to figure out. Since we lacked the authority to delete unused stacks, our work was quite inefficient because many unnecessary stacks accumulated.
I think that an improvement could be made by allowing easy previewing for content managers. I had to guess what I was doing, and having a live preview next to the adjustments could be valuable despite potential technical challenges due to a single stack being used across multiple pages.
I believe that the delete function should be available for everyone because the folders accumulated many empty stacks created by colleagues, making things quite messy. The foldering system was a bit confusing, although I might not recall the details clearly because this was over a year ago.
I have brief experience using Contentstack because my main experience consists of using TeamSite and Tridion before we migrated the contents to Contentstack.
I would advise others looking into using Contentstack to ensure that training is comprehensive and clear, as it could be a good tool, although my experience felt like we were figuring things out without clear guidance.
I understand Contentstack's goal to reuse content instead of creating duplicates, and while I saw a considerable number of empty stacks due to a lack of delete permissions, I see potential in becoming more familiar with it over time. I gave Contentstack a rating of seven out of ten.