[Scoping Item] Match Report Articles in DCAR for Apps

[petternitter]

Let’s scope out what's needed to extend the existing DCR implementation of Match Report articles so it can be served through DCAR and used by the mobile apps.

Match Report articles already render through DCR on web; the work here is to make them compatible with DCAR's architecture, ensuring they can be delivered to the app and maintain feature parity.

Tasks required to deliver this item:

Break down the tasks required to extend Match Report articles from DCR to DCAR and remove any dependency on legacy app templates.

• [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. reuse existing DCR components with minimal modification, defer non-critical enhancements (e.g. styling parity tweaks) to post-migration, 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.