My CMS of choice: ProcessWire

Your advantages:

  • Your projects can be implemented in the way your concept - and not your CMS - intended.
  • A web project in different languages is no problem with ProcessWire - it has functions for multilingualism right from the start.
  • Security. To date there is no known case of a security vulnerability in ProcessWire (this is sometimes somewhat different for competitors).
  • Easy maintenance. And this in two ways: in the sense of a clear and intuitive user interface, but also through:
  • Low maintenance costs
  • It enables system architectures that save you time: You can maintain pieces of information in *one* central location, and the system can output and reuse this data in *many other* locations.
  • ProcessWire is architecturally flexible and developer-friendly - which means you get more for your money than comparable content management systems. Developers* don't have to bend the system into an abstract form before they can start their project - because ProcessWire is technically abstract right from the start and therefore malleable.
  • ProcessWire has a vivid community
  • It is also open source and royalty-free.

No dependence on specialists

You don't depend on a niche system when you choose ProcessWire. It builds on PHP, the widely used programming language on the web, and has an easy-to-learn logic for writing and reading data from databases. It is easier to learn than, for example, peculiarities and compromises of WordPress ("Loop"), Typo3 idiosyncrasies ("TypoScript") and Drupal abstractions!

This means: Developers who are proficient in PHP will also be able to use ProcessWire.

As far as the learning curve for editors is concerned, I've been using ProcessWire for customer projects since 2013 and didn't even have to train customers how to use the user interface once.

Screenshot Backend

Why I recommend it:

ProcessWire is a content management system (CMS) that is adaptable and flexible enough to be suitable for many projects. Besides, it's abstract - it doesn't require the dismantling of blog functionality as a first step, and starting with the actual project features only after (like for example WordPress requires).

Screenshot Backend

ProcessWire has been around since 2012 and since then been constantly evolving. So the system is not a trendy one only to disappear soon, but has proven itself over the last seven years. But it remains flexible enough to deal with new technologies or trends! For example, it is no problem to run ProcessWire as a "headless CMS".

It offers perfect adaptability to individual project requirements: the system manages to balance abstract data storage (so that outputs, filters, lists, individual displays are possible without any problems) with a clear and tidy editorial interface.

Agencies and service providers in Germany and worldwide actively support ProcessWire core development -by contributing their own plugins, modules or through financial support of the project.

But content management system X is more popular!

In my opinion, it's not which system is the most prevalent or widely-used that matters, but rather which system best fits your project, budget and future plans.

If you're concerned that ProcessWire is a niche system where - unlike WordPress and Typo3 - you won't find any developers: Don't worry, you don't depend on ProcessWire and developers need less specialized knowledge than comparable systems.

Many websites do not show that they are built with ProcessWire. However, there is an official "Powered by ProcessWire" directory with projects from many industries.

My services

  • HTML, CSS and JavaScript
  • Inclusive Design/Accessibility
  • Content Management Systems: ProcessWire, Drupal, Kirby
  • PHP Framework: Laravel
  • Concept, audit and consultancy
  • Technical project management

Sounds interesting?

I'm available for new projects starting July 2019. Can I help you building a successful digital product?

Contact me for a cost estimate