fd147f9998
All checks were successful
Deploy to Production / deploy (push) Successful in 1m13s
New @bmm/video workspace at remotion/. Renders an 8s 1920×1080 H.264
+ WebM + JPG poster sequence that visualises the three-step "How it
works" pitch literally:
- Beat 1 (0-2s): "Search our Notion workspace" word-by-word entrance
with spring-in from below + brief indigo under-glow + monospace
prompt.txt label. Blinking cursor bridges the loop seam.
- Beat 2 (2-5s): each prompt word detonates into ~9 particles per
word; particles drift, then magnetically converge onto target slots
along a server schematic that strokes itself on. Scan-line sweep +
corner labels (mcp-notion, OAuth 2.1, search_pages, get_page_content)
sell that this is a real artefact, not a placeholder.
- Beat 3 (5-8s): Claude Desktop client panel slides in from the right;
a Bézier wire animates between server and client; three data-packet
dots travel along the wire; 200-OK tag pops; green live-dot pulses
on the server. Last 12 frames fade to black so frame 239 ≈ frame 0
and browser <video loop> has no visible seam.
Brand palette is hard-coded in lib/colors.ts to match globals.css —
keeps the Remotion bundle self-contained (no Tailwind import needed).
springIn / softSpring / clampLerp / rand helpers in lib/easings.ts
power the motion vocabulary. Concurrency=1 + yuv420p in the config
gives a deterministic render that plays on every <video> tag.
File sizes: hero.mp4 449 KB, hero.webm 258 KB, hero-poster.jpg 33 KB —
all well under the 3 MB / 250 KB ceilings.
Section 2 ("How it works") now opens with the video in a
border-bordered aspect-video panel between the heading and the three
existing cards. autoPlay+muted+loop+playsInline satisfies every mobile
autoplay policy; motion-reduce:hidden swaps in the static poster for
prefers-reduced-motion users.
Scripts:
- pnpm --filter @bmm/video render:all (mp4 + webm + poster)
- pnpm --filter @bmm/video to-web (copy to apps/web/public/videos/)
- pnpm --filter @bmm/video build (both, end-to-end)
`to-web` is the script name because `publish` collides with pnpm's
built-in npm-publish command which refused to run with an unclean tree.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
40 lines
1.3 KiB
JavaScript
40 lines
1.3 KiB
JavaScript
// Copies rendered artifacts from remotion/out/ into apps/web/public/videos/
|
|
// where the marketing page expects them. Run after `pnpm render:all`.
|
|
//
|
|
// Kept as a plain mjs script (no deps) so it works without installing
|
|
// anything in the Web app workspace.
|
|
|
|
import { copyFileSync, existsSync, mkdirSync, statSync } from 'node:fs';
|
|
import { resolve, dirname } from 'node:path';
|
|
import { fileURLToPath } from 'node:url';
|
|
|
|
const __dirname = dirname(fileURLToPath(import.meta.url));
|
|
const SRC = resolve(__dirname, '..', 'out');
|
|
const DEST = resolve(__dirname, '..', '..', 'apps', 'web', 'public', 'videos');
|
|
|
|
const FILES = [
|
|
{ name: 'hero.mp4', maxBytes: 3 * 1024 * 1024 },
|
|
{ name: 'hero.webm', maxBytes: 3 * 1024 * 1024 },
|
|
{ name: 'hero-poster.jpg', maxBytes: 250 * 1024 },
|
|
];
|
|
|
|
mkdirSync(DEST, { recursive: true });
|
|
|
|
let missing = [];
|
|
for (const f of FILES) {
|
|
const from = resolve(SRC, f.name);
|
|
if (!existsSync(from)) {
|
|
missing.push(f.name);
|
|
continue;
|
|
}
|
|
const size = statSync(from).size;
|
|
copyFileSync(from, resolve(DEST, f.name));
|
|
const status = size > f.maxBytes ? '⚠ OVER LIMIT' : '✓';
|
|
console.log(`${status} ${f.name} ${(size / 1024).toFixed(1)} KiB (limit ${(f.maxBytes / 1024).toFixed(0)} KiB)`);
|
|
}
|
|
|
|
if (missing.length) {
|
|
console.error(`\nMissing: ${missing.join(', ')} — run \`pnpm render:all\` first.`);
|
|
process.exit(1);
|
|
}
|