Product walkthrough videos: five one-minute captioned end-to-end flows for launch

Aperta
  • Qualcosa non va?
#1,066 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
content

Direzione di ricerca

Read the five flow descriptions and the linked docs-journey reference in the issue to understand the required narration and pacing. Locate the product screens, sample data, title-card details, and a safe demo stack for each flow; no specific files or entry points are provided. Done means five captioned 1920x1080 H.264 MP4 walkthroughs, each with a matching .vtt file, title cards, complete end-to-end flows, and no exposed credentials.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement post-launch

Five short product walkthrough videos to post publicly at launch, so people can preview the product end to end.

Each video:

  • covers one complete flow, about one minute long;
  • is paced for a viewer to follow: human-speed typing, deliberate pauses, the page scrolled and framed so the part being described is on screen (the docs-journey recordings are 1280x720, unscrolled and at machine speed, so the bottom of taller pages is cut off);
  • has captions burned in, plus a .vtt subtitle file (a voice track can be added later);
  • opens and closes with a title card (product name and URL);
  • is exported as MP4 (H.264, 1920x1080) plus the .vtt;
  • never shows a credential, and is recorded from a real stack with realistic demo data.

The flows:

  1. Getting started: the stack comes up, sign in, a first look around.
  2. First experiment: the guided wizard, the SDK snippet, users arriving, the result with its significance.
  3. Feature flag rollout: create a flag, target a segment, roll out gradually, switch it off instantly.
  4. Automatic safety rollback: errors rise, the safety monitor rolls the flag back on its own, the audit trail shows why.
  5. Plan and team: size an experiment with the power calculator, then invite teammates with roles.

These are separate from the docs-journey recordings (#939), which stay as test evidence. Wanted for launch; the production deploy does not wait for them.

Lingua principale
Python
Stelle
0
Fork
4
Merge medio
5h 36m
PR unite (30g)
509

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Controlvar/controlvar

Tutte le issue di Controlvar/controlvar

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.