Product walkthrough videos: five one-minute captioned end-to-end flows for launch
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 42/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- content
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
.vttsubtitle 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:
- Getting started: the stack comes up, sign in, a first look around.
- First experiment: the guided wizard, the SDK snippet, users arriving, the result with its significance.
- Feature flag rollout: create a flag, target a segment, roll out gradually, switch it off instantly.
- Automatic safety rollback: errors rise, the safety monitor rolls the flag back on its own, the audit trail shows why.
- 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.
- 主要语言
- Python
- 星标
- 0
- 派生
- 4
- 平均合并
- 5 小时 36 分钟
- 30 天内合并 PR
- 509
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Controlvar/controlvar 的其他 Issue
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 72/100
Controlvar/controlvar#1748 ·
维护者通常 1 天内回复
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 68/100
Controlvar/controlvar#1737 ·
维护者通常 1 天内回复
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 70/100
Controlvar/controlvar#1562 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 90/100
Controlvar/controlvar#1447 · 2 条评论 ·
维护者通常 1 天内回复
-
bug post-launch
难度 2/5 1-3 小时 新手友好度 72/100
Controlvar/controlvar#1428 ·
维护者通常 1 天内回复
查看 Controlvar/controlvar 的全部 Issue
相似的 Issue
-
follow-up needs-triage S3: minor
难度 2/5 1-3 小时 新手友好度 72/100
manaflow-ai/cmux#36856 · 1 条评论 ·
维护者通常 1 天内回复
-
documentation good first issue help wanted
难度 1/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
Shell framework build fails at "copy the shader libraries": the iOS shader libraries are now one file b-<chain>.img可能已有人在做 @xiaofeng-han 今天认领。 未关闭build ios
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复