Skip to content

Redesign CADRAGE format selection for web, video, social, and print #1

Description

@tomvaillant

Problem

CADRAGE question 3 currently asks for one destination too early:

Where will this visual appear?
- Social vertical — Stories/Reels
- Social feed — Instagram/Facebook post
- Article web/embed — interactive, image or video

Journalists often need more than one deliverable, especially web plus video. Print is also a legitimate destination. The current single-choice channel model conflates destination, format, and aspect ratio, and it pushes social aspect decisions before the visual concept is settled.

@rmdms

Suggested solution

Replace the current question with a staged production-plan flow.

Stage 1: deliverables, multi-select

Ask what is needed:

  • Web/article
  • Video
  • Social
  • Print

Allow one or several choices.

Stage 2: choose the production path

  • If web is among several requested outputs, start with the web version as the editorial master, then derive or separately route requested video/static variants.
  • If video is the only deliverable, route directly to video.
  • If print is selected, require a static, print-safe output and collect print constraints later.
  • Treat each output as an explicit deliverable tied to the same confirmed takeaway; never silently duplicate or drop one.

Stage 3: defer output-specific dimensions

Ask aspect ratio only when entering a video/social export that needs it. Prefer destination defaults and a lightweight confirmation over asking dimensions during initial CADRAGE. Collect print size/orientation only on the print branch.

The data model likely needs a plural production plan such as deliverables[] instead of one global channel, with format eligibility evaluated per deliverable. Preserve backward compatibility for existing single-channel accepted files.

Acceptance criteria

  • A journalist can request web + video in one CADRAGE response.
  • Video-only requests bypass web production.
  • Print is represented as a first-class deliverable.
  • Aspect ratio questions occur only on branches that require them and after the editorial format is chosen.
  • Every requested deliverable appears in the accepted production plan and final report.
  • Tests cover web-only, video-only, web+video, social+web, and print combinations.
  • No requested output is silently dropped, and one output cannot inherit an incompatible format from another.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions