After our Notion x AMP Learning Circle at SGInnovate on 26 September, I wanted a short recap video for Nasriflix.
What I had: an 80-second recording of me talking to camera, a ZIP of workshop photos, and zero desire to spend an evening in a video editor.
So I did not open one. I asked Notion AI (my Notion agent, Sir Work-alot) to edit the video with Remotion, a framework that builds videos with code. Here is the finished recap, then exactly how it came together.
The final cut: 51 seconds, 1920 × 1080, with burnt-in subtitles and an original music bed.
Why Remotion instead of a video editor
Remotion lets you describe a video as React components: scenes, timings, animations and captions are all just code. That matters for one simple reason. An AI can write code, but it cannot drag clips around a timeline.
With Remotion, the whole edit becomes something my agent can build, check and re-render inside its own computer sandbox. And because it is code, it is repeatable. The next event recap starts from the same pipeline, not from a blank project.
I had already captured the process as a Notion Skill, my Remotion Video Maker, so I did not have to explain the workflow again. I just pointed it at the event.
Step 1: Script first, then record my way
I started with a short read-aloud script on the event's planning page, plus a simple recording checklist: film horizontally at 1080p, camera at eye level, quiet room, and a second or two of silence at each end.
Then I recorded it, and naturally went a little off-script. My version focused more on career profiles, the skills log and a career wins bank. Rather than forcing the script, the edit followed what I actually said. Real beats rehearsed.
Step 2: Cut 80 seconds down to 51
The raw recording ran about 80 seconds. The cut came in at 51, without speeding up my voice. We removed:
- The opening greeting
- An aside about attendance
- A reflection I had repeated
- The sign-off
One thing we deliberately kept: the moment AI features became unavailable mid-workshop and we carried on with the core Notion workflows. It is the most honest part of the story, and it reinforces the whole point of the session.
Step 3: Build the scenes
The video opens on me talking to camera, then my narration continues over seven original workshop photos with gentle zooms and short dissolves. Here is the plan Remotion followed:
Each scene is its own component, stitched together with fade transitions. Photos get a slow Ken Burns zoom so nothing feels static.
Step 4: Check stills before rendering
This is the habit that saves the most time. Before rendering the full video, the agent renders one still frame per scene and checks each one: text wrapping, awkward crops, captions sitting in the wrong place.
Fixing a crop in a still takes seconds. Discovering it after a full render takes much longer. Every scene preview, caption timing and the closing hold were checked before export.
Step 5: Subtitles, music and sound
- Subtitles: 26 timed caption cues, burnt into the video, plus a separate SRT file for platforms that prefer their own captions.
- Music: an original, quiet music bed generated in code to the exact length of the video. No licensing headaches.
- Voice: my source narration was fairly quiet, so it was lifted to a clearer listening level.
The final check confirmed both the video and audio streams in the exported MP4.
Step 6: Ship it to Nasriflix
Nasriflix runs on a Notion database, so publishing was just a matter of placing the MP4 under the Watch section of the event page. The site automatically uses the first uploaded video as a muted, looping cover preview on the event card. No YouTube upload needed.
One technical detail I am quietly proud of: the site uses a stable media link that fetches a fresh Notion file URL each time, so the preview does not break when Notion's download links expire.
A few gotchas worth knowing
If you try Remotion with an AI agent, these will save you some pain:
- Use absolute paths for your public folder when rendering stills, or your images will quietly fail to load.
- Keep styles in named constants rather than inline style objects. It keeps generated files clean and avoids broken braces.
- Wait for the render to fully finish before inspecting or muxing the file. Checking it mid-render just throws errors.
- Normalise your photos first (orientation, size, quality) so phone shots do not appear sideways.
What I took away
- Turn your process into a skill. Once the workflow lived in Notion, making a video became one request, not a project.
- Edit to what you said, not what you planned. The script was a guide. The recording was the truth.
- Keep the honest bits. The AI outage made the recap more real, not less.
- Structure first, then AI. The same lesson as the workshop itself. Clear inputs (script, photos, plan) made the AI edit fast and calm.
I build Notion systems for a living, and I did not expect video editing to fit so neatly into that world. It turns out that once a video is code, it is just another workflow.
If you have a pile of event photos and a quick talking-head clip sitting on your phone, try describing the recap you want before you open an editor. You might not need one.