newsletter id snaps

[dblatcher]

What is the value of this and can you measure success?

[if it works] - including a snaplink (to the API page for a newsletter) on a front will provide enough data in the DCR page model for DCR to render a sign-up widget to that newsletter in the slot that the snaplink was placed.

Should provide a the basis for a DCR-rendered replacement to newsletter thrashers - in theory, should be possible to drop a snaplink in a thrasher slot in the fronts-tool and have DCR render a new component.

What does this change?

• Wires the NewsletterService to FaciaController and Adds the newsletters data to the DCR rendering model for fronts
• defines a new SnapType (FrontendNewsletterSnap ) representing links to the API page for a newsletter (eg https://newsletters.guardianapis.com/api/newsletters/best-of-opinion)
• adds a newsletterId property to SnapStuff

Screenshots

Checklist

• Tested locally, and on CODE if necessary
• Will not break dotcom-rendering
• Will not break our database – if updating CAPI, updated and committed the database files
• Meets our accessibility standards
  • Tested with screen reader
  • Navigable with keyboard
  • Colour contrast passed

[github-actions]

"This PR is stale because it has been open 30 days with no activity. Unless a comment is added or the “stale” label removed, this will be closed in 3 days"

[github-actions]

This PR was closed because it has been stalled for 3 days with no activity.