Bludit VS Wagtail

If you don't mind PHP, Bludit CMS is pretty light and easy. Uses a flat file database. https://www.bludit.com/

https://www.bludit.com/ is a good replacement with a web admin GUI and static pages.

You could try Bludit, it's a lightweight flat file CMS. I've built multiple sites with it. https://www.bludit.com/

> Yes WordPress is bad. I should use a static site generator with nearly free hosting anyways

I operate a few blogs running Bludit[0]. I do this since WP is highly complex. I like to keep it simple. But Wordpress is handy if you're a control freak and love to tinker.

Why do you want a read-only filesystem for WP? I have several WP installs running under XAMPP, and if I want to, I could have a hundred, or...a thousand for testing purposes.

[0] https://www.bludit.com/

Recently, I switched from Wordpress to https://www.bludit.com/ , so far loving it. But then again, I don't need much. Just simple UI, Text, some images in Blogpost and MD to write stuff. That's it.

BoidCMS has similar features to Bludit CMS. How does BoidCMS compare to Bludit CMS?

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.