RFC 53: Swappable Page model

[sonnybaker]

Rendered

[mattlinares]

This would be great. Is this still alive? :)

[NotANormalNerd]

This would be an amazing solution to a problem we have right now. We are not happy with how pages are identified by Wagtail, so we would like to introduce another PageIdentifier. Right now we can have a ParentalKey to another Model but that handling is just not elegant for something that should essentially be a CharField.

I think this would add a lot of value and possibilities to Wagtail Development. And with django-swappable-models there is even some experience here.

[thibaudcolas]

Thank you @sonnybaker for taking a crack at this, I can only imagine it being very tough to write an RFC for this.

Linking to historical discussion for reference: Feature request: Swappability of main models #11381

---

@mattlinares @NotANormalNerd, and anyone who wonders where this is at – if you want to see this happen,

1. Review the RFC and provide feedback
2. Get your friends to review the RFC
3. Discuss this in place with the Wagtail Slack

We’re not particularly good at this RFC process but if there’s movement I’m sure the core team will make efforts to support this.

[sonnybaker]

Hi @thibaudcolas! Thanks so much for resurrecting this. It's fair to say Wagtail has come on a little bit since I wrote this back in 2020, so there's obviously a lot more to factor in now (new revisions sytem and comments immediately spring to mind). We're keen to get behind this at at Hactar, so would love to work on the PR/epic with the guidance of the core team if there's an appetite for it to move forward.

[lb-]

Please note, we have closed the PR wagtail/wagtail#5457 & raised an issue to reflect that goal instead wagtail/wagtail#11440

It might be worth updating this RFC to reflect that in the links section.

[allcaps]

A use-case that could benefit coderedcorp/wagtail-seo#43 (comment)