Skip to content

Production-ready animations, transitions, backgrounds, and scenes for Remotion

feat: added some video practices

kapishdima3122f28f0c74
diff --git a/content/docs/guides/feature-announcement.mdx b/content/docs/guides/feature-announcement.mdx
new file mode 100644
index 00000000..7a2f94d7
--- /dev/null
+++ b/content/docs/guides/feature-announcement.mdx
@@ -0,0 +1,81 @@
+---
+title: Feature announcement
+description: A ~40-second release video that shows the feature working — the one we shipped remocn/ui with
+---
+
+<GuideVideo
+ src="https://cdn.remocn.dev/videos/remocn-ui.mp4"
+ poster="https://cdn.remocn.dev/posters/remocn-ui.png"
+/>
+
+This is the video we announced remocn/ui with. A launch video sells the whole product; a feature announcement sells one release — and it earns its runtime by showing the feature work, not by talking about it. Eight beats, about forty seconds, and the demo beat gets the most screen time.
+
+## The storyboard
+
+1. **The moments** — three quick situations your users know, swapping in one spot, then the problem lands in one line.
+2. **The reveal** — "Meet &lt;Feature&gt;", with your one-line promise.
+3. **The mechanism** — the single idea behind the feature, one calm beat.
+4. **The demo** — the feature acting on camera: a fake app screen doing the real thing. The longest part of the video.
+5. **The breadth** — a fast montage of what else ships in this release.
+6. **The value** — three claims stack up.
+7. **The install** — a terminal types your command or call to action.
+8. **The outro** — your logo, one quiet closing line.
+
+## Your words
+
+Ten blanks:
+
+- **Feature name**
+- **Three moments** — situations where users need it, two to four words each
+- **Problem line** — the claim that lands after the moments
+- **Promise line** — what changes now, one sentence
+- **Mechanism line** — how it works, one plain sentence
+- **Demo actions** — two or three things we should watch happen ("a dialog opens, a menu filters, a form fills itself")
+- **What else ships** — three to six short names; skip this beat if the release is one thing
+- **Three value claims**
+- **Install command or CTA**
+- **Closing line**
+
+Struggling with the lines? [Words on screen](/docs/guides/words-on-screen) is the cheat sheet.
+
+## The prompt
+
+```text
+I'm making a feature announcement video with remocn (remocn.dev).
+
+Build a ~40-second, 1920×1080, 30fps release video for <FEATURE NAME> in this
+Remotion project, using remocn components — install anything you need with
+`npx shadcn add @remocn/<name>`:
+
+1. Hook — three quick moments swapping in one center slot: "<MOMENT 1>",
+ "<MOMENT 2>", "<MOMENT 3>" — then the problem lands beneath them:
+ "<PROBLEM LINE>".
+2. Reveal — "Meet <FEATURE NAME>", then the promise: "<PROMISE LINE>".
+3. Mechanism — one calm beat naming the idea: "<MECHANISM LINE>".
+4. Demo — the feature acting on camera: a fake app screen where
+ <DEMO ACTIONS>. Give this the most screen time — it is the proof.
+5. Breadth — a fast montage of what else ships: <OTHER ITEMS>.
+6. Value — three claims stacking line by line (line-by-line-slide):
+ <THREE CLAIMS>.
+7. Install — a terminal line that types itself: `<COMMAND OR CTA>`.
+8. Outro — my logo (<LOGO FILE, or: use the product name as a wordmark>)
+ with a quiet closing line: "<CLOSING LINE>".
+
+Style: warm dark background (#141318), off-white text, one accent color
+<ACCENT COLOR>, Manrope. One quiet shader-simplex-noise field runs behind the
+entire video with a radial scrim. Keep transitions restrained — crossfades,
+plus one signature transition at the reveal. Use my copy exactly as written.
+```
+
+## Directing the result
+
+- "The demo is too fast — I can't follow what the screen does."
+- "Give the reveal more room to breathe."
+- "Cut the breadth montage — this release is one thing."
+- "The hook moments should swap faster."
+
+More directing vocabulary: [Directing your agent](/docs/guides/directing-your-agent).
+
+## Get the file
+
+Ask your agent: **"Render the video."** You'll get an `.mp4` in the project folder, ready to post.
diff --git a/content/docs/guides/index.mdx b/content/docs/guides/index.mdx
index 338cb240..42a795ae 100644
--- a/content/docs/guides/index.mdx
+++ b/content/docs/guides/index.mdx
@@ -10,6 +10,8 @@ First time here? Do the one-time [Setup](/docs/guides/setup) — about ten minut
## The videos
- [Launch video](/docs/guides/launch-video) — the ~35-second video we launched remocn with, rebuilt around your product.
+- [Feature announcement](/docs/guides/feature-announcement) — a ~40-second release video that shows your feature working on camera.
+- [Showcase reel](/docs/guides/showcase-reel) — a fast reel where every item in a collection gets its own beat.
## The practices
diff --git a/content/docs/guides/meta.json b/content/docs/guides/meta.json
index 107599a6..7dc927a2 100644
--- a/content/docs/guides/meta.json
+++ b/content/docs/guides/meta.json
@@ -6,6 +6,8 @@
"setup",
"---Videos---",
"launch-video",
+ "feature-announcement",
+ "showcase-reel",
"---Practices---",
"how-a-video-is-built",
"directing-your-agent",
diff --git a/content/docs/guides/showcase-reel.mdx b/content/docs/guides/showcase-reel.mdx
new file mode 100644
index 00000000..f427e795
--- /dev/null
+++ b/content/docs/guides/showcase-reel.mdx
@@ -0,0 +1,74 @@
+---
+title: Showcase reel
+description: A fast ~30-second reel where every item in a collection gets its own beat — the one we shipped the typography wave with
+---
+
+<GuideVideo
+ src="https://cdn.remocn.dev/videos/typography.mp4"
+ poster="https://cdn.remocn.dev/posters/typography.png"
+/>
+
+This is the video we shipped eighteen new text animations with. The trick that carries it: nothing is described — every item gets two seconds of stage and demonstrates itself. If you have a collection — templates, integrations, themes, effects — this recipe turns the list into a reel.
+
+## The storyboard
+
+1. **The hook** — one line on why this collection matters.
+2. **The number** — the count lands big. In ours, "18 new text animations".
+3. **The reel** — the heart of the video: one item per beat, a small counter ticking in a corner while items change, each item named with its own motion. If your items are visual, each one demonstrates itself.
+4. **The mechanism** — one line on the property every item shares.
+5. **The value** — two or three claims stack up.
+6. **The close** — a terminal types your command or link.
+7. **The lockup** — your logo and a closing line.
+
+## Your words
+
+- **The collection** — what the things are, and the count
+- **Hook line**
+- **The items** — six to eighteen names, one or two words each. Fewer than six? Make a [Feature announcement](/docs/guides/feature-announcement) instead.
+- **Mechanism line** — the property every item shares
+- **Two or three value claims**
+- **Command or link**
+- **Closing line**
+
+Struggling with the lines? [Words on screen](/docs/guides/words-on-screen) is the cheat sheet.
+
+## The prompt
+
+```text
+I'm making a showcase reel with remocn (remocn.dev).
+
+Build a ~30-second, 1920×1080, 30fps reel for <N> new <THINGS> in this
+Remotion project, using remocn components — install anything you need with
+`npx shadcn add @remocn/<name>`:
+
+1. Hook — an animated headline: "<HOOK LINE>".
+2. The number — the count lands big: "<N> new <THINGS>".
+3. The reel — one beat per item, roughly two seconds each, with a small
+ "NN / <N>" counter holding perfectly still in a corner while the items
+ change: <ITEM LIST>.
+ Vary the motion between items — use remocn's text animations — and where
+ an item can demonstrate itself, let it.
+4. Mechanism — one calm line: "<MECHANISM LINE>".
+5. Value — claims stacking line by line (line-by-line-slide): <CLAIMS>.
+6. Close — a terminal line that types itself: `<COMMAND OR LINK>`.
+7. 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 the reel snappy — no long holds, effect after effect. Use my copy
+exactly as written.
+```
+
+## Directing the result
+
+- "The reel drags in the middle — tighten items six through ten."
+- "The counter is too prominent — smaller and dimmer."
+- "Item four moves like item three — give it a different motion."
+- "Hold the number beat a little longer."
+
+More directing vocabulary: [Directing your agent](/docs/guides/directing-your-agent).
+
+## Get the file
+
+Ask your agent: **"Render the video."** You'll get an `.mp4` in the project folder, ready to post.