Wagtail VS CraftCMS

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.

The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to update our CMS or some user have a weak password, it can be someone outside of our team. WordPress, Drupal, CraftCMS, or Ghost are perfect examples of such CMSs.

I checked one website in that list, it uses CraftCMS, which apparently has htmx bundled. (https://github.com/craftcms/cms/tree/main/src/web/assets/htm...)

Would be interesting to know which other CMS'es make use of htmx (and to what degree).

PHP has a lot of top tier CMSes. IMHO bunch of them are even better than Statamic. Craft CMS (https://craftcms.com/) is a lot more mature database based CMS. Kirby (https://getkirby.com/) is better at flat-file and has a lot better admin interface. Twill (https://twillcms.com/) is better integrated in Laravel and is fully open-source. Statamic mostly feels like it's sitting besides Laravel and they call themselves Laravel based for marketing.

You're basically looking for any CMS that supports headless mode. E.g. Strapi (https://strapi.io/, NodeJS based), CraftCMS (https://craftcms.com/, PHP based) or countless others.

Craft CMS

It's built on Craft CMS. Makes the relationships between elements (a match and a player, for example) super easy.

Is there a reason you aren’t using an existing CMS? There’s a lot that provide all the UI functionality you are talking about and then expose it via a API to be consumed in your front end. https://craftcms.com is one option I’ve had good success with.