Contentstack Adaptive Digital Experience Platform
ContentstackExternal reviews
281 reviews
from
and
External reviews are not included in the AWS star rating for the product.
It is a great powerful tool use and has various features which helps users to solve their problems
What do you like best about the product?
The architecture support they provide understanding your use cases
What do you dislike about the product?
Nothing to dislike in particular about contentstack
What problems is the product solving and how is that benefiting you?
We are using it for our business use case and it is helping us in fetching static content
Best Composable CMS
What do you like best about the product?
The CMS feature set and ease of use are best of breed. There really isn't anyone doing it better. Modular blocks and content modeling are extremely intuitive.
What do you dislike about the product?
The inline preview and edit tags can get quite complicated to debug. A simpler solution to WYSIWYG would make the product stand out against the competitors.
An odd one that I run into all the time is the lack of "Folders". An implementation of taxonomy in a way to create simulated folder view at a minimum would resonate so well with many customers who are coming from content systems that have them.
An odd one that I run into all the time is the lack of "Folders". An implementation of taxonomy in a way to create simulated folder view at a minimum would resonate so well with many customers who are coming from content systems that have them.
What problems is the product solving and how is that benefiting you?
CMS and composable layout manage ment.
Best Headless CMS and DXP in the market.
What do you like best about the product?
From a data (content) perspective, the ability to build and refine model contents has the ability to unlock tons of value. Pair this with their App Maketplace for turn-key integrations and you have an amazing CMS. Great so now you can properly store and manage content, your ready to tap into some of the other great features like Automate and Launch. Combining all of these product offers can truly enable your business to reach its goals.
What do you dislike about the product?
Traditionally the documentation has been great, but the guided education and community part of the platform is still in its early stages.
What problems is the product solving and how is that benefiting you?
Content managment at scale which includes the ability to structure content for better insights as well as having the ability to transfer the published content to any number of channels.
Sr Manager, Tech Partnerships
What do you like best about the product?
Ease of use, product funcitionality and enterprise readiness
What do you dislike about the product?
Nothing comes top of mind, they are great all around
What problems is the product solving and how is that benefiting you?
Helps our customers and prospects realize the true value of a composable architecture and modernize thier web applications
G2 is bursting onto the scenes in a great way!
What do you like best about the product?
Contentstack is an excellent system to seamlessly manage & create content in many different platforms/environments. It is incredibly easy to use and setup. It is one of the main systems we use at work. It is a breeze getting up to speed on it!
What do you dislike about the product?
There is some redundancy in the submissions/versions that can get hairy. Often times you find yourself with 50 different versions of a project and no idea how it got there with minor edits.
What problems is the product solving and how is that benefiting you?
Contentstack is solving the time management and simultanious updating problems that we have. It saves us a lot of time by having multiple people working on the same project at the same time.
CMS Reviews
What do you like best about the product?
I like the ease of use and the UI design. The workflow is simple and the fast, it improves my workflow.
What do you dislike about the product?
Not sure I have dislikes, possibly the seperaton of modules and having to need to publish the page vs individual components.
What problems is the product solving and how is that benefiting you?
Sinergizxing all our systems. The headless aspect allow us to be nimble and innovate for our clients.
Great UI
What do you like best about the product?
Has an amazing UI, and I like that it can evolve as the company grows. It is easy to implement into our everyday work.
What do you dislike about the product?
Not being able to incorporate other programs that we use in the office. Having everything under one app would be amazing.
What problems is the product solving and how is that benefiting you?
As a developer its a great tool, with contnet management.
Developer Friendly Multichannel support
What do you like best about the product?
Developer friendly.
Authoring Friendly.
Developer/Author Commenting/discussions on fields level.
Can be accessed anywhere.
Rest API support.
Good customer support
Easy to integrate.
Support for GraphQL is good. Have to improve.
Very flexible to create content models.
User friendly UI.
Workflow easy to configure.
Ease use of Roles and ACL
Authoring Friendly.
Developer/Author Commenting/discussions on fields level.
Can be accessed anywhere.
Rest API support.
Good customer support
Easy to integrate.
Support for GraphQL is good. Have to improve.
Very flexible to create content models.
User friendly UI.
Workflow easy to configure.
Ease use of Roles and ACL
What do you dislike about the product?
1. There is no Navigation support, like If I need to have site nav in the front end.
2. The level of nesting is restricted till level 4. maximum reference depth limit should be more.
3. Unpubished content is not accessible more than 1 nested level in CMA API.
4. The UID is not same within different branch level.
5. The UID is not same within different stack level.
6. There should be an UID which should be same accross all branch and all stack for a content (It can be unique within Organisational level)
7. The Title change of a content creates a new entry on migration to another branch or stack.
8. Front end Branch merge should be there with a Rollback option.
9. Front end content stack to stack migration should be there.
10. The limit of nested entries should be more than 100 count.
11. There should be a Rollback option of Content Types.
12. Automation hub execution is costly.
13. The customization of OOB should be allowed more.
14. Taxonomy should allow the content to be mapped under another content.
15. Timely backup should be there. or restore point should be there.
16. RTE should have more features.
2. The level of nesting is restricted till level 4. maximum reference depth limit should be more.
3. Unpubished content is not accessible more than 1 nested level in CMA API.
4. The UID is not same within different branch level.
5. The UID is not same within different stack level.
6. There should be an UID which should be same accross all branch and all stack for a content (It can be unique within Organisational level)
7. The Title change of a content creates a new entry on migration to another branch or stack.
8. Front end Branch merge should be there with a Rollback option.
9. Front end content stack to stack migration should be there.
10. The limit of nested entries should be more than 100 count.
11. There should be a Rollback option of Content Types.
12. Automation hub execution is costly.
13. The customization of OOB should be allowed more.
14. Taxonomy should allow the content to be mapped under another content.
15. Timely backup should be there. or restore point should be there.
16. RTE should have more features.
What problems is the product solving and how is that benefiting you?
Mutlichannel access.
Easy to maintain and implement.
Easy access.
Integration.
Developer and Author friendly.
Rest API and graphQL.
Easy to maintain and implement.
Easy access.
Integration.
Developer and Author friendly.
Rest API and graphQL.
Simplifying Page Creation for Non-Tech Teams
What do you like best about the product?
With Contentstack we enable the non-tech teams in our company to create landing pages without engineering support. Since we are in control of Contentstack, we can make sure that these teams follow a specifc page strcuture (by creating a defined template where they just populate the content) or allow them to be as creative as they want (by creating components that they can drag & drop and create the page the way they need).
We now have more around 10 non-tech teams creating more than 10 pages per day. This includes the Localisation team which uses a plugin to connect Contentstack to their L10n tool. Every time we create a new page, the team is notified automatically so they can work on it.
Contentstack also gives us great customer support. We have quarterly meetings with them, but it's also very easy to communicate with them if we need some urgent support, either via chat or via email
We now have more around 10 non-tech teams creating more than 10 pages per day. This includes the Localisation team which uses a plugin to connect Contentstack to their L10n tool. Every time we create a new page, the team is notified automatically so they can work on it.
Contentstack also gives us great customer support. We have quarterly meetings with them, but it's also very easy to communicate with them if we need some urgent support, either via chat or via email
What do you dislike about the product?
Even though the UI is good in general, there are some cases where it could be improved. For example, if a page has a lot of fields, it can get very messy and hard to understand the content hierarchy.
Global fields are not very intuitive. We assumed that they would work in a certain way and then we made a small change in one global field that resulted in a massive loss of data. Thankfully, the support team helped us to retrieve the pages. The UI, however, didn't alert us that this would happen if we preceeded
Global fields are not very intuitive. We assumed that they would work in a certain way and then we made a small change in one global field that resulted in a massive loss of data. Thankfully, the support team helped us to retrieve the pages. The UI, however, didn't alert us that this would happen if we preceeded
What problems is the product solving and how is that benefiting you?
* Creating landing pages for our product without engineering support --> it helps us deliver faster
* Localising content for all global markets we target
* Easy update the content in our landing pages
* Localising content for all global markets we target
* Easy update the content in our landing pages
The easiest way to build a website
What do you like best about the product?
Changes are super easy to make and you can personalize your page as much as you want. The interface is super user-friendly. I use it on a daily basis with my team. They can be autonomous even if they have no programation skills, which is great added-value.
What do you dislike about the product?
The fact when you change the name of a picture after having uploaded it, if you search for this new name, it is not taking it into account. Only the first name of an image can be used in the search field.
What problems is the product solving and how is that benefiting you?
In the past, we were using a very old software that required programming skills. It preveneted us from having the whole team working on the website. Contentstack is completely solving this issue.
showing 31 - 40