Comments on: Why choose ProcessWire over WordPress?

By: Lukas

Lukas — Fri, 07 Jul 2017 14:53:15 +0000

ProcessWire is such a powerfull CMS and this is just a great article that highlights all the benefits and reasons, why to choose ProcessWire.

I have worked a lot with PW but always had the problem to start each project from scratch because of missing high quality templates/themes. And the limitation to easily have a Blog-structured website.

Thus I decided to combine the work I’ve done and prepare a couple of premium, flexible templates and offer them at https://pwtemplates.de

Have a look at the demos and I you like them, you can purchase them for a small expense allowance. Hope you like it!

By: Michael

Michael — Wed, 13 Aug 2014 11:26:51 +0000

In reply to Pwired. Nice comment, that summarises my entire post :)

By: Pwired

Pwired — Tue, 12 Aug 2014 15:38:38 +0000

That´s right. With processwire you can make your own (any) template with your own html and css.
Then put php with processwire api between the tags and pull anything you want from the database
that you have entered with the admin of processwire. The admin uses a page and field system to enter,
edit, and setup content and data with your own types. Most people use it´s potential for a flexible and
scalable cms but internally it is more of an engine that can drive a cms, cmf, interfaces, applications, etc.

By: Michael

Michael — Tue, 06 Aug 2013 09:06:52 +0000

In reply to organizedfellowOrganizedFellow. Very nicely said.

By: organizedfellowOrganizedFellow

organizedfellowOrganizedFellow — Tue, 30 Jul 2013 14:01:59 +0000

Regarding the themeability and templating nature of WordPress and ProcessWire …

ProcessWire doesn’t have one.
If you know html/css/js well enough, you can create you own totally custom site. This is far different than WordPress and does not even warrant a comparison. Simply checkout all the various html template websites. WordPress themes/templates are always offered separate from the similar html/css offerings.
WordPress is tough to theme, HTML is always simpler. That’s part of the immense beauty that is ProcessWire.
You design it how you want. Custom fields galore!

By: maykel

maykel — Sat, 09 Feb 2013 16:37:16 +0000

In reply to Ian.

@Ian yes, I was aware of that and did not see it as a problem on PW. But WP still have this feature on by default as if all users would want to switch themes every week or so.

I may need to rephrase that point to avoid misunderstanding 🙂

By: Ian

Ian — Sat, 09 Feb 2013 15:56:14 +0000

@maykel, maybe not 1 click, but you can swap the templates via FTP using 2 commands: rename the folder “templates” to “templates-old” and “templates-another” to “templates. Piece of cake! 😀

By: maykel

maykel — Wed, 06 Feb 2013 01:39:19 +0000

In reply to Rasmus Schultz.

What I meant with #8 was that you do not need “one-click to change the theme” feature and have folders of different themes on the working directory.

I have worked with few WordPress specialists over different projects and to my astonishment they always could bend over backwards to make the design work. Long documentation was required though to make the user know to update it, which is why I feel it is still not ideal.

Thanks for sharing your thoughts.

By: Rasmus Schultz

Rasmus Schultz — Tue, 05 Feb 2013 18:03:08 +0000

I’m puzzled by number 8 – what do you mean by that?

Having complete freedom and flexibility on the front-end is one of the biggest selling points for ProcessWire for me – unlike other platforms like WordPress or Drupal (or really almost any other CMS/blog platform) nothing is set in stone when it comes to the presentation/front-end.

To me, this is one of the most brilliant things about ProcessWire – it’s the only CMS (or platform at large) where I never have to tell the designer, “we can’t do that”, when it comes to the front-end. Where most other platforms use some kind of theme framework for rendering, ProcessWire simply provides building blocks, gets out of the way, and lets you do whatever you want.

On my personal top 10, that would be number 1. 🙂