Contentful vs. Decap CMS

It's a great all rounder for content projects. It's easy in the basics and powerful in the complex, data heavy scenarios. Extending the platform is straightforward and the SDK gives you everything you need. If you have many many varying content types , it gets expensive and perhaps not the best choice .

Incentivized

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

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

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

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

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

It is a very easy to use and configure application. I find that it is on the user to manage the content after the models have been created, yet I still do not encounter issues finding or creating new components for our site. It is easy to set up and easy to navigate.

Incentivized

For custom solutions, Contentful blows every other CMS I've used out of the water. Unlike WordPress, there's no clutter to wade through, and you can simply build the infrastructure you need. It's more secure by far, and works seamlessly with modern frontend technologies, like GatsbyJS. In contrast to website builders like Squarespace and Wix, Contentful gives developers (like myself) free range to create high-quality, unique, scalable frontends that aren't limited by preexisting design and layout structures.

Incentivized

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

• Contentful has saved us valuable development time that was previously spent doing deploys for minor content updates.
• Contentful has helped us maintain consistent documentation, reducing time needed to review for consistency.
• Can't say we've really experienced any negative ROI impacts from using Contentful, but we've run into some limitations in adding too many content models and the next pricing tier is substantially more expensive.

Incentivized

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized