Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

## Unreleased

**docs/talk: Get started comes first, Contact last**
- Why: the maintainer is using the page as the project's homepage (the repo's About link) and asked for a homepage order: how to start right after the title, contact details at the end.
- `docs/talk/index.html`: "Get started" is section 01, right after the title (the commands, and what happens next with the three sign-offs and the effort levels); a new last section, "Contact", holds the GitHub and WeChat QR codes, the email and the footer. The other sections move down one number. The speaker notes, the nav, the key list (`Home` / `End`) and `docs/talk/README.md`'s script follow the new order; the talk still runs about 4.5 minutes.

**docs/talk: a one-page site and script for a five-minute demo**
- Why: the maintainer is presenting the project at a small Claude meetup and asked for a page that carries the intro film, the project's story and its films, in English, saying that Claude wrote it, plus the words to say.
- `docs/talk/index.html`: ten full-screen sections (why, what it adds, architecture, the intro film, the films, the style library, who wrote it, how the author uses it, getting started) that move with a clicker or the arrow keys, with speaker notes (`N`), a five-minute timer (`T`) and a key list (`?`). The films play from `tools/fetch_media.sh`'s local copies when they are there and stream from the `media` release otherwise. A live f(t) panel draws a Fourier square wave as a pure function of time and checks it: the same frame drawn again after another one, compared pixel by pixel. The PR numbers (73 in nine days, 70 from `claude/` branches) come from the repo's pull request list on 2026-10-09.
Expand Down
31 changes: 18 additions & 13 deletions docs/talk/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# A five-minute demo of OpenVideoHarness

`index.html` is a one-page site for presenting the project in about five minutes: why it exists, what it adds, the architecture, the intro film, the films it made, the style library, who wrote it, how the author uses it, and how to start. Claude wrote the page and the script below.
`index.html` is the project's one-page site, and the page for presenting it in about five minutes: how to start, why it exists, what it adds, the architecture, the intro film, the films it made, the style library, who wrote it, how the author uses it, and how to get in touch. Claude wrote the page and the script below.

## Viewing it

Expand All @@ -18,7 +18,7 @@ GitHub's file view shows the HTML source, not the page. To see the page:
```
Without them the page streams from the GitHub release. Press `N` on the film section: the notes say which source it is using.
3. Your own material, all optional:
- **WeChat QR**: save it as `docs/talk/img/wechat.jpg` and the "Say hi on WeChat" card appears next to the GitHub QR. Without the file the card stays hidden; with notes on, the page says it is missing. Committing the image makes it public with the repo.
- **WeChat QR**: save it as `docs/talk/img/wechat.jpg` and the "Say hi on WeChat" card appears next to the GitHub QR in the Contact section. Without the file the card stays hidden; with notes on, the page says it is missing. Committing the image makes it public with the repo.
- **Douyin and Bilibili links**: paste them into the two empty `href=""` in the "In the wild" section.
- **The Nobel explainer**: put the file at `docs/talk/media/nobel.mp4` (git ignores that folder) and a player shows up in the "In the wild" section.
4. Check the time once: `T` starts the timer, `R` resets it.
Expand All @@ -31,6 +31,7 @@ GitHub's file view shows the HTML source, not the page. To see the page:
| `←` `↑` `PgUp` | previous section |
| `Space` | play or pause the film on the film section; next section elsewhere |
| `1`–`9`, `0` | jump to section 1–9, 10 |
| `Home` / `End` | the first / the last section (Contact) |
| `N` | speaker notes for the current section (and the film's source) |
| `T` / `R` | start or pause the timer / reset it |
| `F` | full screen |
Expand All @@ -46,41 +47,45 @@ About 300 words of speech (2:20 at a relaxed pace) plus the 1:43 film. "Be done
> Hi everyone. This is OpenVideoHarness: a video workbench for Claude Code.
> Our motto: not more tools. Know-how.

**2 · Why** (0:50)
**2 · Get started** (0:30)
> First, how you use it: one line to install, then open Claude Code and ask for a video in one sentence.
> It stops three times for your sign-off: the direction, the storyboard, the first draft.

**3 · Why** (1:05)
> It started with Opus 5.5. Its video code has real taste: motion, type, pacing.
> We already have great engines, like HyperFrames and Remotion. But an engine just renders frames. It doesn't give you the idea, the storyboard, the script, or the style.
> So I talked it through with Claude, and we built that missing layer: the whole workflow, from idea to final cut.

**3 · Features** (1:15) *optional: drag the f(t) slider while you talk*
> What does it add? It starts with ideas, not code. It has nine workflows, one for each kind of video. You sign off three times: direction, storyboard, draft.
**4 · Features** (1:30) *optional: drag the f(t) slider while you talk*
> What does it add? It starts with ideas, not code. It has nine workflows, one for each kind of video.
> And since Claude can't watch video, it checks its own frames and audio, and a second Claude scores the draft.

**4 · Architecture** (1:35)
**5 · Architecture** (1:50)
> The architecture is simple. Claude Code reads CLAUDE.md, our router. It picks a video type, pulls in the playbook, styles and templates, and drives the engines through one CLI.
> And every project writes its lessons back into the docs.

**5 · The intro film** (3:25) *Space to play; the page dims while it plays*
**6 · The intro film** (3:40) *Space to play; the page dims while it plays*
> Here's our intro film. Claude made it with the harness itself.
>
> *(1:43 of film)*

**6 · Works** (3:45) *click "What Claude sees" on the second sentence*
**7 · Works** (4:00) *click "What Claude sees" on the second sentence*
> A few more films, each from one sentence: a science short, a 3Blue1Brown-style explainer, and Clawd, hand-drawn.
> And this is what Claude sees when it reviews them: not video. Contact sheets.

**7 · Styles** (3:55) *skip this line if you are short on time*
**8 · Styles** (4:08) *skip this line if you are short on time*
> Plus thirty-one styles to borrow from, so not every film looks the same.

**8 · Built by Claude** (4:15)
**9 · Built by Claude** (4:25)
> And the code? In nine days the repo got seventy-three pull requests. Seventy came from Claude.
> I bring the taste and the decisions. Claude writes the rest.

**9 · In the wild** (4:35)
**10 · In the wild** (4:42)
> I use it myself, too. I post films made with it on Douyin and Bilibili.
> When this year's Nobel Prize in Physics was announced, I had an explainer out about three hours later.

**10 · Get started** (4:50) *leave the QR codes up for questions*
> It's open source. One line to install, then just ask Claude Code for a video.
**11 · Contact** (4:55) *leave the QR codes up for questions*
> It's open source. Scan the code to star it, or add me on WeChat.
> Thank you!

## Where the numbers come from
Expand Down
Loading
Loading