Changelog video

Not every release deserves a launch. Most weeks ship three or four small improvements — a fix, a speedup, a new option — and that's exactly what this video carries. About twenty-five seconds, no big reveal, posted on a rhythm: weekly, monthly, every release. It's the lightweight sibling of the Feature announcement — when one change deserves the spotlight, use that recipe; when the week shipped several small things, use this one.

The storyboard6

1. 1
   The stampYour product name and the date or version land together, like a postmark. This is the recurring open viewers learn to recognize.
2. 2
   Item oneThe change's name and one line on what it does.
3. 3
   Item twoSame shape, next change.
4. 4
   Item threeSame shape again. If a change is visual, show it instead of describing it.
5. 5
   The nudgeOne line pointing to the full changelog.
6. 6
   The lockupYour logo, one short closing line.

The value of this video isn't any single edition — it's the rhythm. Same open, same pace, every release. By the third one, viewers recognize your update in the feed before they read a word. So resist redesigning it each time; change the items, keep the frame.

Your words5

Product name

• <PRODUCT NAME>

Version or dateWhatever you stamp releases with

• <VERSION OR DATE>

Three or four changesEach a name plus a one-line payoff, six words or fewer

• <CHANGE 1> — <PAYOFF 1>
• <CHANGE 2> — <PAYOFF 2>
• <CHANGE 3> — <PAYOFF 3>

Changelog URL

• <CHANGELOG URL>

Closing linee.g. "Shipping weekly"

• <CLOSING LINE>

The prompt

Paste it into your agent with your words in place of the highlighted blanks.

I'm making a changelog video with remocn (remocn.dev).

Build a ~25-second, 1920×1080, 30fps release update for <PRODUCT NAME> in
this Remotion project, using remocn components — install anything you need
with `npx shadcn add @remocn/<name>`:

1. Stamp — "<PRODUCT NAME>" with "<VERSION OR DATE>" beneath it, landing
   together like a postmark. Short and confident — this open repeats every
   release, so keep it simple enough to reuse.
2. Items — one beat per change, every beat built the same way: the change
   name lands first, its payoff line follows beneath it:
   - "<CHANGE 1>" — "<PAYOFF 1>"
   - "<CHANGE 2>" — "<PAYOFF 2>"
   - "<CHANGE 3>" — "<PAYOFF 3>"
   If a change is visual, replace its text beat with a small fake app
   screen showing it happen.
3. Nudge — one calm line: "Full changelog at <CHANGELOG URL>".
4. Lockup — my logo (<LOGO FILE, or: use the product name as a wordmark>)
   with a closing line: "<CLOSING LINE>".

Style: warm dark background (#141318), off-white text, one accent color
<ACCENT COLOR>, Manrope. One quiet shader-simplex-noise field behind the
whole video. Keep motion restrained and identical across the item beats —
this is a stamp, not a show. Use my copy exactly as written.

Directing the result

• Item two runs long — tighten it.
• Hold the stamp a beat longer.
• Change three is visual — show the screen instead of the words.
• The items feel different from each other — make the motion identical.

Next release, don't start over — ask your agent to reuse this video and swap the version and the items.

Get the file