CommonSpot vs. Contentstack

Commonspot is well suited for web content management to be conducted by individuals with low-level web skills.

Incentivized

In the most recent project in which we used Contentstack, the client requested to host their text content via CMS so that their Content Editors could manage the text and layout without requirements for developer intervention. Contentstack worked fine for this solution, however there is a worry that the solution was perhaps over engineered - as the site was relatively small and uncomplicated

Incentivized

• I think CommonSpot's greatest strength is its ease of use. It's relatively intuitive in it's usage, so it therefore makes it easy to train new people to use it.
• Within my usage of it, our options were limited, which again added to it's ease of use.

Incentivized

• Content update
• content omnichannel
• content modeling
• Intuitive interface, very easy to use

Incentivized

• Commonspot needs to improve on its authoring feature. It is impossible to author on more than one page at a time . (One must always click on "View work on all changes") before switching between pages otherwise, the changes will not be saved.
• CommonSpot does not support sharing the definition of any custom element or any template layouts. Therefore, one must recreate these in each site.
• In Commonspot, a user who has to manage content in multiple sites will have to log in to each site to see and act on any actions.

Incentivized

• Fiddly setup
• The image tools, whilst good, are less than intuitive

Incentivized

I had no previous background in content management, and found it very easy to use. If I could figure it out, I am pretty certain that just about anyone else could as well.

Incentivized

Commonspot works in tandem with Zendesk very well to accomplish tasks an an efficient manner.

Incentivized

Before deciding on Contentstack, we researched some tools, we chose it because of the ease of creating and changing content, the API options for querying content, the ease of modeling new content APIs, high capacity of the CDN to deliver content, ease of integration with other tools and GraphQL support.

Incentivized

• I was working in a religious institution and based upon our usage and audience, there was no ROI to speak of. Our usage was more for providing information than having any type of interaction. In that instance, it worked very well.

Incentivized

• Easy to manage the site
• Could hand control over to the content chaps
• Simple tweaks to site and wording could be implemented with no dev hours

Incentivized