Easter 2027 is March 28: a spring menu promo from five photos

Easter Sunday 2027 falls on March 28 and Good Friday on March 26, according to year-calendar.com's Easter 2027 page (read 2026-10-12). A 20-second promo built from five photos, a generated music bed and burned-in caption cues costs $0.425 in Sume rates.

March 28 is early: only six days after March 22, the earliest possible Western date. Orders for hams, hot cross buns and brunch tables land in the two weeks before, so one reusable clip with only the cue text swapped each week beats a new shoot.

When should the clips go out?

Work back from the date. The table counts days from today's check date, 2026-10-12, to the date on the source page.

What goes in the five photos and the cues?

Use four seconds per photo: storefront, the special (hot cross buns, a glazed ham, a brunch table), a staff shot, the counter, and an address card. Cues are phrase-level overlay text with start and end seconds, so the clip needs no speech. Suggested cues: "Easter orders open" (0 to 4), "Pre-order by Mar 24" (4 to 12), "Open Good Friday" (12 to 16), "Find us on Main St" (16 to 20). Swap the order-by date to your own cutoff.

How do I build it with the Sume API?

Import the photos first (POST /v1/media-imports), because Timeline only accepts files already hosted on media.sume.com. Each call returns a job: poll GET /v1/jobs/:id/status and read GET /v1/jobs/:id/result for the video_url. POST /v1/timeline-1.0/plan is unbilled and returns the duration and estimated cost before you render. The placeholder URLs below are examples only.

# 1) bed: POST /v1/music-router/generate (prompt: instrumental gentle spring piano bed, 20 seconds, no vocals) -> audio artifact
# 2) five imported photos (media.sume.com URLs) over a silent spine + bed
curl -X POST https://api.sume.com/v1/timeline-1.0/render \
  -H "Authorization: Bearer $SUME_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: easter-2027-is-march-28-spring-timeline-001" \
  -d '{"audio":{"mode":"silence","duration_seconds":20},
       "video":[{"source_url":"https://media.sume.com/artifacts/artf_demo/photo1.jpg","start":0,"duration":4},
                {"source_url":"https://media.sume.com/artifacts/artf_demo/photo2.jpg","start":4,"duration":4,"transition":{"type":"fade","duration":0.5}},
                {"source_url":"https://media.sume.com/artifacts/artf_demo/photo3.jpg","start":8,"duration":4,"transition":{"type":"fade","duration":0.5}},
                {"source_url":"https://media.sume.com/artifacts/artf_demo/photo4.jpg","start":12,"duration":4,"transition":{"type":"fade","duration":0.5}},
                {"source_url":"https://media.sume.com/artifacts/artf_demo/photo5.jpg","start":16,"duration":4,"transition":{"type":"fade","duration":0.5}}],
       "soundtrack":{"url":"https://media.sume.com/artifacts/artf_demo/bed.mp3","gain_db":-6,"fade_out_seconds":2}}'
# 3) burn authored cues on the finished MP4
curl -X POST https://api.sume.com/v1/video-captions \
  -H "Authorization: Bearer $SUME_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: easter-2027-is-march-28-spring-captions-001" \
  -d '{"video_url":"https://media.sume.com/artifacts/artf_demo/timeline.mp4","style":"slam","cues":[{"text": "Easter orders open", "start": 0, "end": 4}, {"text": "Pre-order by Mar 24", "start": 4, "end": 12}, {"text": "Open Good Friday", "start": 12, "end": 16}, {"text": "Find us on Main St", "start": 16, "end": 20}]}'

What does the 20-second version cost on Sume?

The photos are yours, so there is no generation line. Rates come from the Sume docs: Music Router charges $0.125 per generation, Timeline 1.0 charges $0.10 per ceil(output minute), and a standalone caption job is $0.20. Check GET /v1/catalog, the live catalog, before you budget. Four weekly variants that only change cues cost 4 x $0.20 = $0.80 in caption jobs, since you reuse the rendered MP4.

When is this the wrong approach?

A photo slideshow with cues is the cheap, fast option, not the right tool for every job.

• You want original footage of the food: stills will not read as a shoot.
• Your hours change often: post text, since a rendered clip does not update itself.
• You need a named licensed track: the bed is generated, instrumental and original.