When comparing ProcessWire vs Netlify CMS, the Slant community recommends ProcessWire for most people. In the question“What are the best open source headless CMS's?” ProcessWire is ranked 4th while Netlify CMS is ranked 6th. The most important reason people chose ProcessWire is:
You will always find one to respond politely in the forums. Sometimes even the creator Ryan Cramer himself.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Nice and helpful growing community
You will always find one to respond politely in the forums. Sometimes even the creator Ryan Cramer himself.
Pro Custom Fields on steroids
ProcessWire is heavily based on custom fields. All objects (Pages) inside ProcessWire are based on extensible templates comprised of fields that can be easily defined. Many useful fields come prebuilt and they can be extended with modules.
Pro Easy to learn
Processwire is extremely easy to learn. Consider this:
echo $pages->get('title=Hello World')->title; // "Hello World"
echo $pages->get('title=Hello World')->parent->title; // "Home"
echo $pages->find('Template=Category')->count; // 126
echo $pages->find('Template=Category')->each('title'); // ['Audio', 'Video' …]
Selectors are so powerful but yet so easy.
Check out the cheatsheet.
Pro Powerful and easy API
The API is jQuery like;
// find some pages:
$pages->find('template=skyscraper, architect=john, sort=title')->limit(4);
// mutate
$pages->get('title=Hello You')->set('title', 'HelloWorld')->save();
$pages->get('title=Old')->trash(); // trash page
// check user…
$user->isLogedin();
echo $user->name; // guest
$session->login($name, $pass);
$session->logout();
// redirect
$session->redirect($url);
Pro Powerful selector engine
The way you fetch, access and manipulate objects (Pages) in ProcessWire is extremely powerful and easy. You can receive any page and its custom fields, filter, travers, add…
Pro Template Engine Agnostic
By default, ProcessWire comes with 0 assumption on how you handle the output. You have 100% freedom on how you want to develop the frontend. Want to plain output stuff, go ahead. Want to use any number of Templating Engine, do it. Just use as Headless-CMS, okay!
Pro Extensible
Either using the modules already available or writing your own module, using the jQuery-like API.
Pro Open source
Source available on GitHub.
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.