Skip to content

Story 2096: Impliment Wagtail Integration#2100

Open
jlchilders11 wants to merge 5 commits intoboostorg:developfrom
jlchilders11:jc/wagtail-integration
Open

Story 2096: Impliment Wagtail Integration#2100
jlchilders11 wants to merge 5 commits intoboostorg:developfrom
jlchilders11:jc/wagtail-integration

Conversation

@jlchilders11
Copy link
Collaborator

Implement Wagtail Integrations:

Mixins

  • FlaggedMixin - Adds a custom serve method to prevent unflagged users from seeing this page
  • TaggableMixin - Adds the ability to tag pages for categorization

Routing

  • RoutableHomePage - New home page for all wagtail interactions that allows for forwarding routing to child pages, e.g. if you get to wagtail through /outreach/, you will be routed through the OutreachHomePage

Posts

This is the bulk of the work, and is a porting of the existing Entry Model to Wagtail

  • PostIndexPage - Index Page for Posts, implements most of the logic in formatting found in the news.views.EntryListView. NOTE: this uses queryparams for filtering the child pages, rather than seperate URLs
  • PostPage - Functional translation of Entry, but uses a stream field rather than having separate models for different types of content. These can be filtered by the content of the stream field block

NOTES:

  • Additional work/discussion is needed on the PollBlock. Currently this is not implemented, as it is disabled in the existing architecture, and will be non trivial to implement in Wagtail
  • Additional work is needed for the video block to both automatically save the thumbnail, and display it instead of autoloading the video.

DEPLOYMENT NOTES:
When deploying this, a RoutableHomePage should be created and the existing OutreachHomePage should be moved under it to respect the new routing methods.

@jlchilders11 jlchilders11 changed the title Story 2096: Implment Wagtail Integration Story 2096: Impliment Wagtail Integration Feb 26, 2026
Copy link
Collaborator

@gregjkal gregjkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per our conversation in standup: please test the homepage to make sure it won't break without manually migrating the existing testimonial and/or news items. If it does break, we need to either make these changes backwards-compatible (my strong preference!), with a follow-up change that cleans any bridge code up, or add a data migration so it can be fixed during the deploy instead of crashing until manual fixes.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please avoid multiple migration files in a single PR if they can be combined.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Regenrated the Migrations, and confirmed that the home page and testimonials are unaffected by this change and do not need to be moved to function properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants