Story 2096: Impliment Wagtail Integration#2100
Story 2096: Impliment Wagtail Integration#2100jlchilders11 wants to merge 5 commits intoboostorg:developfrom
Conversation
gregjkal
left a comment
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Please avoid multiple migration files in a single PR if they can be combined.
There was a problem hiding this comment.
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.
Implement Wagtail Integrations:
Mixins
FlaggedMixin- Adds a custom serve method to prevent unflagged users from seeing this pageTaggableMixin- Adds the ability to tag pages for categorizationRouting
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 theOutreachHomePagePosts
This is the bulk of the work, and is a porting of the existing
EntryModel to WagtailPostIndexPage- Index Page for Posts, implements most of the logic in formatting found in thenews.views.EntryListView. NOTE: this uses queryparams for filtering the child pages, rather than seperate URLsPostPage- Functional translation ofEntry, 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 blockNOTES:
DEPLOYMENT NOTES:
When deploying this, a
RoutableHomePageshould be created and the existingOutreachHomePageshould be moved under it to respect the new routing methods.