Task: Serve Wagtail and Legacy Entry News at the same Endpoint

[jlchilders11]

Context

Currently, the wagtail integration of the News feed is served at a bespoke endpoint (/pages/news/) and the legacy News feed is still served at the expected endpoint /news/. Originally the intent was to do this switchover at part of the go live, but this is now no longer acceptable as it adds too much over head in the case of rollbacks. This ticket addresses this requirement.

Scope

1. Both the Wagtail and Legacy News feeds are served at /news/, with the actual displayed feed being determined by the v3 flag on the request.
2. The Legacy news feed should be fed by the Entry model, the Wagtail news feed should be fed by the PostPage model.
3. Plausible should count both of these models as the same, since they share the same URL.

Out of scope

• Any changes to the creations, deletion, or moderation flows for either model. This is strictly a display change.

Acceptance criteria

• Users with the v3 Flag who visit /news/ receive the Wagtail workflow and v3 Design experience
• Users without the v3 Flag who visit /news/ receive the Legacy workflow and v2 design experience
• Users are able to create, edit, and delete their posts from both flows

[herzog0]

Update :: Jeremy and I are discussing internally about the approach on a a few key things:

• User redirection to the correct URL when the v3 flag is switched;
• Plausible counting updates;
• Legacy vs Wagtail served posts;