Netlify CMS vs Plone
When comparing Netlify CMS vs Plone, the Slant community recommends Plone for most people. In the question“What are the best open source headless CMS's?” Plone is ranked 3rd while Netlify CMS is ranked 6th. The most important reason people chose Plone is:
Not only does this provides complete transparency to the user, it also enables a large base of developers to work simultaneously on solving any arising the issues and improving the platform.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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
Pro Open source
Not only does this provides complete transparency to the user, it also enables a large base of developers to work simultaneously on solving any arising the issues and improving the platform.
Pro Remarkable level of security
Plone has been around for almost two decates and to date less than 50 vulnerabilities were discovered in the platform. That's at least ten times less than any of the popular alternatives, including Wordpress, Drupal, and Joomla. In fact, government agencies, such as NASA and FBI use Plone for its high level of security.
Pro Can run on virtually anything
Plone runs on Windows, Mac, Linux, Chromebooks, RaspberryPi, servers, and cloud services.
Pro Multilingual UI and documentation
Plone platform along with all documentation is available in more than 40 languages, including Chinese, Japanese, Greek, Arabic, and Hebrew.
Cons
Con A lot of configuration
Example: a few plugins and some code are needed for gatsby-img or markdown to work.