Modernise for latest Wagtail and Django

[nickmoreton]

Working with Wagtail 4.1

This is a rework of the Longclaw master branch that adjusts the code for working with Wagtail 2.15+ but makes a few other changes, for now, to hopefully re-boot a Wagtail package that always looked so promising.

I am happy to hear any feedback 😄

What is fixed

It's opinionated but...

• It requires Wagtail 2.15+ (LTS) and Django 3.2+ (LTS)
• The original tests run OK.
• Tox is modernised and runs in github actions, along with coverage.
• I think I have made the test app work better for a developer.
• Developer setup is improved without been too different.
• The admin site works well, especially nice with Wagtail 4.1
• The orders Dashboard is moved to it's own admin page, at least for the moment.

What not fixed / removed / broken

Although I haven't included some original code there's no reason It couldn't be added back in.

• Not fixed, frontend client side CSS/JS
• The templates could do with some work.
• The project_template isn't included now.
• The documentation needs attention, mainly to update it to the latest Wagtail version.
• Shopping basket
• Checkout
• And may be something else you see and fancy getting involved in!

[nickmoreton]

I've added GitHub Actions but have seen random failures with loading the countries there. It doesn't happen locally.

[JamesRamm]

This is a big PR.
In theory I would be happy for it to be merged, as it is important, but the issues would need to be fixed first.
I.e you have pointed out a few things that are in a broken state. The project_template is fairly important just because the entire documentation directs you to create a new shop using this, so if that is broken no-one will be able to on-board.

If it is tricky to fix all issues in this PR, I would suggest trying to break it up into more atomic updates. E.g one PR for updating wagtail, one PR for modernising tox and github actions and so on. 7

This will make it much easier to review and merge

[nickmoreton]

Thanks @JamesRamm Yep it's a big one 😄 you could say I got carried away but I think it shows the way forward.

I'll find some time to break it down into smaller pieces of work so it can be reviewed easier and merge in bit by bit.

[JamesRamm]

@nickmoreton do you feel like going further with this PR?

[nickmoreton]

@nickmoreton do you feel like going further with this PR?

Hi @JamesRamm Yes I would. I’ve not had time to work on it since the PR due to other work. I’ll see what I can do to break it down into smaller pieces of work.

[nickmoreton]

Hi @JamesRamm I made a start: #485

What do you think? Thanks