← Back home

See Content Forge in action

The full demo video is in production. Below is the script we’re recording — a 45–60 second walkthrough of the pipeline from topic to publish-ready assets.

Demo video coming soon

Content Forge — Demo Video Script

Target length: 45–60 seconds
Format: Screen recording with voice-over + light background music
Aspect ratio: 16:9 (YouTube) or 9:16 (Shorts/Reels/TikTok)


Scene 1: Hook (0:00–0:08)

Visual: Dark-themed dashboard, camera slowly zooms in.

On-screen text: “What if AI wrote your blog posts end-to-end?”

Voice-over:
“What if you could drop in a topic and get a researched, SEO-optimized blog post with a cover image — automatically?”


Scene 2: Create a job (0:08–0:20)

Visual: Click “New Job,” type topic “The future of serverless AI workflows,” select tone “Professional,” length “Medium,” click “Run.”

On-screen text: “Topic → Tone → Go”

Voice-over:
“Enter a topic, pick your tone and length, and hit run. Content Forge handles the rest.”


Scene 3: Pipeline in motion (0:20–0:35)

Visual: Job detail page. Progress bar moves through Research → Outline → Draft → SEO → Image → Notify. Each stage completes in real time.

On-screen text: “Research → Outline → Draft → SEO → Image → Notify”

Voice-over:
“It researches, outlines, writes the draft, optimizes for SEO, generates a cover image, and emails you when it’s done.”


Scene 4: Result + exports (0:35–0:48)

Visual: Scroll through finished draft. Click “Export” and select PDF, then PowerPoint.

On-screen text: “Markdown • HTML • JSON • PDF • PowerPoint”

Voice-over:
“Export as Markdown, HTML, JSON, PDF, or PowerPoint. Or schedule recurring posts so your content never stops.”


Scene 5: CTA (0:48–0:60)

Visual: GitHub repo page and live app URL side by side.

On-screen text: “Open-source on GitHub” / “Try the live demo”

Voice-over:
“Content Forge is open-source. Star it on GitHub and try the live demo today.”


Production notes

  • Record in dark mode for visual consistency.
  • Use smooth cursor movements and quick cuts between stages.
  • Keep text overlays large and readable on mobile.
  • Add subtle whoosh sound effects when stages complete.
  • End with a 2-second pause on the GitHub CTA.