Page Structure — Which arc carries the story best?

All three use the C → D → A narrative. The difference is pacing and how hard the sections hit.

HOOK (dark, full-screen)
Running agents is like managing a team
with no shared memory.
RELIEF (white)
One init. Every agent reads the same state.
HOW IT WORKS (light alt)
init → exec → dispatch → relay
FEATURES (white, rich cards)
Context · Dispatch · Capability · Relay
OS VISION (dark, cinematic)
synlynk is the OS layer for multi-agent dev.
JOIN WAITLIST (accent band)
Early access → config + team management
BLOG PREVIEW + FOOTER

A — Narrative Scroll

Page tells the story top-to-bottom like a long-form essay. Each section is a chapter. Dark hero → light relief → dark OS vision creates strong rhythm. Works best for someone who reads the whole page.

HERO (dark, split layout)
Hook headline
Sub-hook copy
→ Get started ○ Join waitlist
$ synlynk init
✓ project-docs/ created
✓ claude.md injected
✓ 3 agents configured
$ synlynk dispatch claude
→ job-a3f2 queued
PAIN → SOLUTION (white, alternating)
Problem statement → feature that fixes it × 3
OS VISION (dark)
The bigger picture.
WAITLIST + BLOG + FOOTER

B — Demo First

Split hero: hook headline on left, live-looking terminal output on right. Shows the product in 5 lines before explaining it. Draws in the developer who wants to see before they read.

CHAPTER 1 — THE PROBLEM (dark, cinematic)
"No shared memory.
No coordination.
Just noise."
CHAPTER 2 — THE FIX (white)
One init. Install line. Instant relief.
CHAPTER 3 — THE SYSTEM (light alt)
How dispatch · context · relay fit together
CHAPTER 4 — THE VISION (dark)
Multi-agent OS. Where this is going.
CHAPTER 5 — JOIN (accent, full-width)
Waitlist. Early config access.
BLOG + FOOTER

C — Chapter Structure

Explicit chapter breaks with dramatic chapter-1 open — bold headline, minimal copy, maximum tension. Each chapter is a beat. More like a product launch page than a docs site.