Unclaimed: Are are working at Contentstack ?
Contentstack Reviews & Product Details
Contentstack is a company based in San Francisco that’s built to offer API-first headless CMS. The platform is built to empower marketers and developers to collaborate around content to create customer journeys and deliver dynamic digital experiences across channels, audiences, brands, and regions. It is Microservices-based, API-first, Cloud-native SaaS, and Headless.
| Capabilities |
|
|---|---|
| Segment |
|
| Deployment | Cloud / SaaS / Web-Based, Desktop Mac, Desktop Windows, Mobile Android, Mobile iPhone, On-Premise Linux |
| Support | 24/7 (Live rep), Chat, Email/Help Desk, FAQs/Forum, Knowledge Base, Phone Support |
| Training | Documentation |
| Languages | English |
Compare Contentstack with other popular tools in the same category.
Easy to deploy, easy to use at every level, and it helps us push push digital content quickly saving us alot of time.
There's nt much to complain about yet. I would appreciate more customized features in the future though!
We use this as our primary (and only) CMS tool for managing and updating digital content.
I really like the ease of use of the platform!
Sometimes is a little bit slow, UI could be better
We can easily change content in our website!
The basics of Contentstack is pretty easy to learn with enough onboarding and material on hand. I was able to learn and execute changes on Contentstack in less than a week.
Unfortunately, Contentstack is limited in functionality and aesthetic-wise. While there are many great features, there is not much flexibility to edit specific components to your liking. Also, the appearance of a Contentsack website could be improved (i.e., more flexibility to use with different designs, etc.)
For our website, Contentstack allows configurations suitable for our products and our industry. For example, the simple but efficient layout of Contentstack pages makes UI/UX easy for customers to navigate.
Headless Adaptability and partnership to adapt roadmap Good performance Good customer support Easy to use
Pricey compared to other options. The pricing model is overcomplicated and difficult to project in time for long-term contracts.
It's allowing us to empower our content teams to self-manage the content globally in a self-serve way, so increase our efficieny.
I like that things get so confusing and messy that I'm the only one that can make things work. That's good for job security.
The rich text editor is really buggy, and you have to use the html to make things work, which limits the population that can effectively use the platform. There are ways to make subtle mistakes in project setup that can set you back weeks when you later realize that things won't work as expected. The ways that entries are connected are not intuitive at all, although this might have been due to how our developers built our first project. The localizations and language settings also created majjor confusion, and we need to rebuild an entire site to correct discrepancies. This should have been anticipated during an onboarding and should have been avoided. (We built two sites that had different master languages, and now we want to modularize our content, which will require rebuilding one so that the language settings match.) I often experience lags that get really annoying when I'm repeating the same sequence of key strokes over and over again. It might be because we're hosting the site on another continent, though. A half second delay per click gets to be a lot when you do thousands of clicks per sub-project. The way that searches work and that search results are displayed could be improved. If you navigate away from a sorted list of search results and then hit the back button (in the platform or on the browser) you lose the sorting, or the specific results page that you were looking at, for example. Finally (for now), we have a bug that requires saving and publishing instead of just publishing. It's not clear why saving should be a required step. Save should mean save without publishing. Publish should mean save and publish, in our opinion.
It's letting us modularize content and have a single source of truth.
Ease of use, UI, ease of integration and depth of features
The content editor and preview function is lacking and I tend to use a third party and paste in the copy.
It's freed up more time for developers and made my job much easier.
I really like how easy is to create content and manage it once you are familiar with the UI.
The UI is not intuitive. I experienced both, the old and the new UI and I think the old one was more intuitive but less appealing.
We use Contentstack for storing articles information. We then query CS from our services and retrieve all the information to render it in our websites.
The user interface is very easy to use which makes the flow of creating content-types/pages really simple. Along with the UI being easy, the API's are also easy to use to fetch/manage content and the documentation to support it is very well written. They do a great job of listening to feedback and they continue to keep building out great products to support your projects. The support is very responsive and has been super helpful along the way.
While some of the UI is simple to use, I think their could be some improvements on the usability side when working in a content-type. Tap/drag targets are somewhat limited. I also wish their were a few more variations of walkthroughs for product integrations that come from the Marketplace or from custom integrations.
Contentstack replaced our old CMS which was very much a 1-to-1 option so building templates was very strict. With Contentstack we're able to build a website the way we want and use the same content-type/modeling for various templates/pages because the headless approach is much more flexible with the front-end development.
All content in one place, easy for design team to work with development team
New UI takes minimalism to the point that it can be difficult to make changes or find items.
Design team can make changes without requiring development team to make code changes.
Easy to collaborate with designers and engineers.
Doesn't work well with apps like grammarly.
Easy to create content without having coding experience or working inside the HTML to add tags etc