We (@dwyl) have used Wagtail in the past because the client (NHS) forced us to. 🔫
We subsequently spent (wasted) 2 sprints trying to extend and optimise it ⏳
what the project(s) needed was something much simpler and more flexible from the start. 🏍
If the CMS does not optimise for accessibility or performance "out-of-the-box"
we will spend all our time building with the CMS only for our end-user's time to be wasted
with slow page-loads and inaccessible content.
Wagtail...?
It should be "safe to assume" that https://wagtail.io is made using the Wagtail CMS: it's unclear from: https://builtwith.com/?https%3a%2f%2fwagtail.io ... what is clear is that they are using a "Kitchen Sink" approach: https://builtwith.com/detailed/wagtail.io
The https://webhint.io stats for the https://wagtail.io website: 148 errors:
Lighthouse Score: 62% for accessibility and 67% for performance.
https://cssstats.com/stats?url=https%3A%2F%2Fwagtail.io
If the CMS does not optimise for accessibility or performance "out-of-the-box" we will spend all our time building with the CMS only for our end-user's time to be wasted with slow page-loads and inaccessible content.
relates to: https://github.com/club-soda/club-soda-guide/issues/5