Skip to content

[Scoping Item] Newsletter Sign-up Articles in DCAR for Apps #14715

@petternitter

Description

@petternitter

Let’s scope out what's needed to extend the existing DCR implementation of Newsletter Sign-up articles so it can be served through DCAR and used in the mobile apps

Newsletter Sign-up articles already work correctly in DCR for web. The goal here is to make them compatible with DCAR, ensuring they integrate correctly with the app, communicate with the native layer where needed to maintain expected functionality (including sign-up form behaviour and dark mode support), and remove any reliance on the legacy app templates.

Tasks required to deliver this item:

Break down the tasks that would need to be done to serve Newsletter Sign-up articles in the app through DCAR and remove any dependency on the current legacy app template. Be sure to capture dark mode support as part of the scope.

  • [Insert task here]
  • ...
  • ...

These tasks will become sub-issues we can pick up after scoping is complete.

Dependencies and risks:

Note anything that could affect sequencing, effort or delivery, e.g.

  • Other teams, services, or APIs not owned by our team this depends on
  • Technical risks or unknowns we should explore further before picking up this work
  • Other factors or concerns that could block progress

Simplification opportunities:

Are there any ways we could reduce effort or complexity, e.g. minimise native bridging, reuse web error states, reuse existing DCAR design tokens for dark mode etc.?

Briefly outline how this would change the DCAR experience from the current experience.

If nothing applies, please note N/A.

Effort: x / 5 Confidence: High / Medium / Low

Notes / links:

Add any useful references, e.g. code, related issues, PRs, examples, or additional context.

Definition of done:

  • Tasks required to deliver the item have been identified and can be converted into sub-issues.
  • Dependencies, risks, and any simplification opportunities are captured.
  • Effort and confidence have been scored.
  • Reviewed by/paired with another engineer on the team.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions