When comparing Superdesk vs ProcessWire, 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 Superdesk is ranked 10th. 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 Visual
The interface is clean and well designed. You can tell someone with a UX background worked on it and not just software engineers.
Pro Easy to use
Putting together an article is straightforward: you type the text into the main fields and then use drag and drop to add photos.
Pro Publish to more than one website
You have the option of setting up publishing routes to choose where something gets published in case you have multiple websites.
Pro Customizable
I like that you can set up a personal workspace and also add different widgets to your dashboard depending on what you’re interested in.
Pro Newsroom automation
Superdesk can aggregate and automate multiple mundane newsroom jobs.
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.
Cons
Con Sometimes buggy
Sometimes, when trying to publish a post I was getting errors which was a bit annoying. However, after we updated to the latest version the instance was running smoothly.
Con Not one-click publishing
At least in our company’s system you need to do a couple of extra steps to publish an article.