mirror of https://github.com/hanzoai/video.git synced 2026-11-03 04:21:39 +00:00

Files

T

calesthioandHanzo Dev 7ffb943132 Initial release — OpenMontage: the first open-source agentic video production system

11 production pipelines, 47 tools, 124 agent skills.
Supports cloud APIs (fal.ai, OpenAI, ElevenLabs, Suno, HeyGen, Runway) and
free local providers (diffusers, Piper TTS, WAN 2.1, Hunyuan, CogVideo).

Co-authored-by: Hanzo Dev <[email protected]>

2026-03-29 08:25:17 -07:00

2.2 KiB

Raw Permalink Blame History

Publish Director - Screen Demo Pipeline

When To Use

Package the finished demo so the user can publish it quickly and so the metadata reflects the actual task, result, and tools involved.

Prerequisites

Layer	Resource	Purpose
Schema	`schemas/artifacts/publish_log.schema.json`	Artifact validation
Prior artifacts	`state.artifacts["compose"]["render_report"]`, `state.artifacts["idea"]["brief"]`, `state.artifacts["script"]["script"]`	Video, brief, and sections
Playbook	Active style playbook	Thumbnail and copy tone

Process

1. Build Searchable Metadata

Screen-demo titles work best when they combine:

task,
tool,
outcome.

Good patterns:

How to deploy on Vercel from Next.js
Fix CORS in React + Express
Set up GitHub Actions for Python tests

Pull keywords from:

software names,
frameworks,
commands,
exact error text,
outcome words such as deploy, fix, connect, publish, ship.

Use script sections as the basis for chapter markers and packaging bullets. A good screen-demo package makes the workflow skimmable before the user even presses play.

3. Thumbnail Strategy

If a thumbnail concept is needed, it should show:

the result state, not a generic setup screen,
the recognizable tool surface,
2-4 words of value text.

Store the concept in publish_log.metadata.thumbnail_concepts.

4. Package By Platform

Prepare:

video file,
title and description/caption,
chapter markers where relevant,
keyword list,
thumbnail concept notes.

For developer or product-demo content, also package:

commands shown,
software/version mentions,
error terms if it is a troubleshooting demo.

5. Quality Gate

metadata names the real tool and task,
chapters match the actual rendered flow,
export folders are clean and reusable,
copy is tailored to the platform instead of duplicated.

Common Pitfalls

Publishing with generic titles that omit the actual software or task.
Using the same caption for YouTube, LinkedIn, and short-form social.
Building chapter markers from the script without checking the render.

2.2 KiB Raw Permalink Blame History