When comparing ProcessWire vs WordPress, the Slant community recommends ProcessWire for most people. In the question“What is the best PHP CMS?” ProcessWire is ranked 1st while WordPress is ranked 9th. 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 Complete control if needed
If you set up WP on your own server, you can change every single aspect of it as you see fit.
Pro Widely used
According to some statistics, WP powers a fifth of the Internet. It means there are resources for everything. Community support, tutorials, extensions and a plethora of customization options.
Pro Self-host & WP-host options
For free WordPress can be hosted by yourself on your own server, or as a subdomain of wordpress.com. You can also pay to use a custom domain with WP hosting.
Pro Open source
Anyone can view the code of WordPress since it's under a libre/open source license.
Pro RSS feeds for everything
Including tags and categories.
Pro Post-level privacy controls
Each post can have a different access level.
Cons
Con A bit of bloat and complexity
WP has grown past being just a blogging platform and as such it's not as lightweight as it used to be. It also considerably more complex due to many more customization options compared to other solutions.
Con Dated
The code is a mess, uses dated conventions, and relies on dated technology.