[Scoping Item] Remove App Slideshow's Dependency on Legacy Templates

[petternitter]

Let's scope out what’s needed to migrate the app's Slideshow feature and remove any dependency on the legacy app slideshow template.

This includes, but is not limited to, understanding how slideshows are currently rendered in the app, how images and captions are sourced, what behaviour (e.g. fullscreen, any swiping logic etc) should be carried over, and how this logic can be implemented or reused within DCAR

Tasks required to deliver this item:

Break down the tasks that would need to be done to serve the app's Slideshow feature in DCAR and remove any dependency on the current legacy app template.

• [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 DCAR gallery/lightbox functionality, drop low-value feature parity, 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.