# How to make a product launch video from code

Write the video as a config file in your repository: the scenes, a voice-over, music, captions and a theme. One command
renders it into an MP4, a WebM, a poster image, a GIF and a caption file. Because the video is built from the repo, the next
release can rebuild it instead of someone re-editing a timeline.

## Steps

1. **Create a starter video.** Run `kinhin video init launch` in your repository. It writes a starter config under
   `.kinhin/videos/`.
2. **Write the scenes.** Title, statement, stats, steps and code scenes are drawn, so they need no screen recording. The
   [video config reference](https://kinhin.dev/guide/video-config.md) lists every scene and setting.
3. **Build it.** Run `kinhin video build launch`. Flags change the theme, format, captions and music for one build.
4. **Find the output.** It lands in `.kinhin/videos/out/launch/`: `launch.mp4`, `launch.webm`, `launch-poster.png`,
   `launch-hero.gif` and the caption file.

## What you need

- A container runtime. kinhin uses Apple's `container` if it is running, otherwise Docker.
- Disk space. The first build pulls a container image of about 1 GB.

No accounts are needed. To rebuild the video in CI on every release, see [Marketing video in CI](https://kinhin.dev/guide/ci-video.md). That is
off by default and opt-in per repository.

For an example, see the [video gallery](https://kinhin.dev/guide/video-gallery.md). Or read [Add videos to your project](https://kinhin.dev/guide/videos-for-your-project.md)
for the full walk-through.

## Next steps

- [Quick start](https://kinhin.dev/guide/quick-start.md): From zero to a working fleet
- [Install](https://kinhin.dev/guide/install.md): Pinned versions, updates and uninstall
- [Forge support](https://kinhin.dev/guide/forges.md): What has been run against a real server
- [Why kinhin](https://kinhin.dev/guide/why-kinhin.md): Why most runners do one job at a time
