When comparing Strapi vs Netlify CMS, the Slant community recommends Strapi for most people. In the question“What are the best open source headless CMS's?” Strapi is ranked 1st while Netlify CMS is ranked 6th. The most important reason people chose Strapi is:
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Auto-generate REST APIs
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Pro Users, groups and permissions
Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.
Pro Out-of-the-box administration panel
Easy way to manage your application. This panel allows you to add/edit/delete entries for your APIs, manage your users, groups and permissions. In the future, it will be such as WordPress-like administration panel dedicated to your application.
Pro Experimental support for GitHub's GraphQL API
Experimental support for GitHub's GraphQL API is now available for the GitHub backend. Without mutation.
Pro Easy Creating Custom Widgets option
The NetlifyCMS exposes a window.CMS global object that you can use to register custom widgets, previews, and editor plugins. The same object is also the default export if you import Netify CMS as an npm module. The available widget extension methods are listed here.

Pro Modern

Pro Open-source

Pro Built in React.js
Cons
Con A lot of configuration
Example: a few plugins and some code are needed for gatsby-img or markdown to work.
