-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task/cdd 2169 new landing page cms #1781
base: main
Are you sure you want to change the base?
Conversation
5f14c34
to
cd63baa
Compare
cd63baa
to
49bab1f
Compare
Quality Gate failedFailed conditions |
@@ -0,0 +1,6 @@ | |||
from django.apps import AppConfig |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was your reasoning behind making an entirely new wagtail app for this?
What stopped you from just making a new LandingPage
model within the home app? That way it would be referred to as home.LandingPage
instead of landing_page.LandingPage
.
In my mind, the app name describes the logical grouping
|
||
content_panels = Page.content_panels + [FieldPanel("sub_title"), FieldPanel("body")] | ||
|
||
api_fields = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you add the list from the base page, you don't need to repeat the seo fields here:
api_fields = UKHSAPage.api_fields + [
APIField("title"),
APIField("sub_title"),
APIField("body")
]
3) The path of the current page. | ||
This always returns an empty string | ||
e.g. `""` | ||
This is because the homepage is assumed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is because the homepage is assumed | |
This is because the landing page is assumed |
@@ -4,6 +4,7 @@ | |||
create_composite_page, | |||
create_bulk_downloads_page, | |||
create_landing_dashboard_page, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth renaming this old handler ot be create_home_page
, so its a bit clearer.
That's my bad, I saw my name against the git blame for that. Which in my defence was way before we embarked on the actual landing page re-work 😄
Then also rename your new one to just be create_landing_page
or something like that
"type": "section", | ||
"value": { | ||
"heading": "Respiratory viruses", | ||
"page_link": None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Presumably we're gonna have to come back and slide the links in for the topic index pages here?
And can the frontend handle when we don't send a link
Description
This PR includes CMS updates for the new
LandingPage
Fixes #CDD-2169
Type of change
Please select the options that are relevant.
Checklist: