ProcessWire VS Wagtail

Processwire is exactly what you want

I use ProcessWire for this kind of site; clients have always been super happy with it. If anything it's more intuitive than WordPress for the client -- all content is laid out in a tree view for them.

ProcessWire

For the ProcessWire project. I created this simple Inertia adapter. And also a sample ProcessWire + Svelte + Laravel Mix + Inertia project.

Build a technical framework (i use Processwire with some manual adjustments) on which I base my freelance projects on. this saves a lot of time during the development because I don´t have to start from scratch

This post could have been me, for when discovering ProcessWire (https://processwire.com/) after 10-ish years of Drupal (also trying out Joomla, Wordpress, Typo3... (well tried installing it at least) and perhaps a few others).

The main differences would be that in Processwire, you don't even need to install plugins, as all different types of displays are so easily created from scratch in the pure-PHP templates, using PW's extremely awesome jquery-like API for getting content (see the cheatsheet for an idea: https://cheatsheet.processwire.com/).

If you like Python 🐍 then check out this project. Wagtail is a popular CMS, combining Django’s powerful customization capabilities with a slick user interface. The newest update brings Django 5.0 support, a new searchable and filterable listing UI, the accessibility checker built into the admin interface, and a brand new 10-step tutorial for developers. This release marks Wagtail's 10th birthday 🎂. Happy birthday to the team and all the best for the next ten years and beyond 🥳.

Repo : https://github.com/wagtail/wagtail

- The discussion thread we use to track all public feedback: https://github.com/wagtail/wagtail/discussions/9553. Comments very welcome.

Not so long ago, I submitted a Pull Request in wagtail to improve the admin performance, especially for non-superusers. Basically, it caches all the user's permissions on first access. However, I was pretty sure that this would load a lot of model fields that we never need but there isn't a tool that gives us that type of report. Therefore, I started building an app that keeps track of all fields accessed so you can easily know which ones haven't been used and apply the only/defer optimisation for Django querysets.

Wagtail would be a good example https://github.com/wagtail/wagtail/tree/main/wagtail/tests

Paarth moving from no contributions to the 21st most contributions - https://github.com/wagtail/wagtail/graphs/contributors.

Over the last few years, I have had the incredible opportunity to be a core team member of the Wagtail project. In that time, I have reviewed many new pull requests, and I’ve also had the chance to submit many of my own across Wagtail and many other projects.

Wagtail 2.15 is the most recent LTS (Long Term Support) release, so it’s not a bad release to stick to at all, at least until February 2023.