Contentful vs. Strapi

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 )

Incentivized

1. If a headless CMS is needed. 2. Need the cms UI to be clean. 3. There is a need for customization options in the UI and API as well. 4. Expertise in javascript and need cms with node js backend. 5. Want auth APIs pre-made. 6. Easy to customize the backend as well. 7. The user interface can be fully customizable.

Incentivized

• 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.

Incentivized

• Free and open source.
• CMS UI is nice and clean.
• Customization options.
• Regular updates and bug fixes.
• Easy to find and understand docs.
• Blogs available to learn more.
• Plugin eco system.

Incentivized

• 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.

Incentivized

• Tutorial videos.
• Use typescript for it's backend.
• Detailed explanation of commands available.
• More clear docs for releasing.

Incentivized

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.

Incentivized

• 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

Incentivized

• Easy to setup.
• Customize the ui.
• Increased productivity.
• Get prebuilt auth apis.
• Customize the backend and add new apis.

Incentivized