-
Notifications
You must be signed in to change notification settings - Fork 947
WT-334 - Build CMS Components For Advertising Pages - Part 4 #16848
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
base: main
Are you sure you want to change the base?
WT-334 - Build CMS Components For Advertising Pages - Part 4 #16848
Conversation
…dark-section css files
…ol, and m24 sizing.
…o mozorg/advertising/landing.html
…334-cms-components-for-advertising-sub-navigation
…nto WT-334-cms-components-for-advertising-other-sub-pages
since line breaks are needed on the 'Impact' page
since rich text is needed on the 'Impact' page
…components-for-advertising-subpage
…334-cms-components-for-advertising-sub-navigation
…f github.com:mozilla/bedrock into WT-334-cms-components-for-advertising-sub-navigation
…nto WT-334-cms-components-for-advertising-other-sub-pages
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #16848 +/- ##
==========================================
+ Coverage 79.70% 79.97% +0.27%
==========================================
Files 159 161 +2
Lines 8534 8825 +291
==========================================
+ Hits 6802 7058 +256
- Misses 1732 1767 +35 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| - dev | ||
| - test | ||
| - stage | ||
| - prod |
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.
Heya - were these changes in action.yaml deliberately backed out, or does this branch need a rebase on main?
| env: | ||
| LONG_SHA: ${{ needs.build_and_publish_public_images.outputs.long_sha }} | ||
| DEPLOYMENT_REALM: ${{ needs.build_and_publish_public_images.outputs.deployment_realm }} | ||
| DEPLOYMENT_ENV: ${{ needs.build_and_publish_public_images.outputs.deployment_env }} |
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.
Same here - I wouldn't expect us to need to back out these changes. Can we rebase / check 'em please?
…334-cms-components-for-advertising-sub-navigation
…nto WT-334-cms-components-for-advertising-other-sub-pages
…components-for-advertising-subpage
…334-cms-components-for-advertising-sub-navigation
…nto WT-334-cms-components-for-advertising-other-sub-pages
If this changeset needs to go into the FXC codebase, please add the
WMO and FXClabel.This pull request depends on #16815, which should be reviewed first
One-line summary
This pull request makes the other advertising subpages ('Solutions' and 'Impact') editable through Wagtail.
Significant changes and points to review
Following the work in #16815, this pull request adds:
ContentSubpageas a child ofAdvertisingIndexPageStatisticCalloutBlockandStatisticBlockFeatureListWithModalsBlock,FeatureItemWithModalBlock, andFigureBlockIssue / Bugzilla link
WT-334
Testing
To test locally,