Likelihood to Recommend Well suited for our needs of multiple images for auto auctions from a variety of sellers. Pointing them to one platform is easier than attempting to use a variety of platforms as we were doing before (email, slack,
Dropbox and
Google Drive would randomly be used by a variety of employees )
Read full review Best suited for large organizations where everyone knows how to deal with Java in an increasingly Java unfriendly world. Said organization should be willing to pay a huge price for a piece of dinosaur technology
Read full review Pros Flexible. This CMS can be easily extended and provide access to dynamic content Simple. The WYSWG is very easy to work with and identifying pages and content in the system is fairly easy Clean Interface. The interface is clean and uncluttered keeping focus on the content and not other factors. Read full review Separate CMS environment publishes to remote server environment - great for security Highly scalable Full scale workflow allows for custom routing, approving, etc.. Read full review Cons Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either. There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly. A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through. Read full review One word: JAVA! We don't live in the 1990's anymore! An AJAX/DHTML environment seems a long time coming. Horrible end-user experience, learning curve. Our end users' inability to easily use the archaic, Java-based interface, means they send the web developer their content requests. This creates a huge bottleneck and completely defeats the purpose of a CMS. Image mangement and integration with content is aweful and time consuming. An image processing tool called ImedImage was developed for Percussion at one point, and left completely stagnant with very little support. Implementation is extremely complicated, given the complexity of the system. Sure, scalability is a good thing, but there is very little out-of-the box function. Don't expect to implement a site as quickly as with other CMS platforms. Read full review Alternatives Considered In the past we've used
WordPress to manage documentation content.
WordPress was more flexible than Contentful but also prone to inconsistencies and we ended having a lot of hacks to accomplish various
WordPress tricks. With Contentful there's less ambiguity so content producers are less likely to go astray. We also have our own in-house programmatic template solution for managing content, but this was a previous pain point when we needed to get the dev team to do a deploy for every content change.
Read full review No contest. I can't wait to get off of Percussion CMS.
Read full review Return on Investment Positive - new hires are able to get onboarded quicker with us using Contentful Positive - we can customize the journey of what modules/material the user sees after a course/video/article Positive - it's been an overall game changer when hiring external candidates who need extensive training Read full review We are locked into Percussion CMS simply due to the expense and complexity of migrating to another solution (and the lack of time and budget to do so). I long for the day when I am no longer required to support Percussion CMS, to say the least. Read full review ScreenShots —