Files
cv/public/media/how-it-works.en.vtt
T
dong.nguyen e02fe19bbe video: point explanations at the diagram, extend scenes for readable dwell
Explanations become Callout chips (kit.tsx): a leader line draws from the
target element, the chip fades in only after the line completes, timed to
the scene beat. The fixed bottom bullet row in SceneChrome is deleted.
Leaders stop at element outer edges; chips sit fully outside each visual
group (Pipeline push callout narrowed clear of the group box).

Timeline 62s -> 81s (2425 frames): every callout holds >=150 frames after
it appears; scene beats unchanged, hold time added at each scene end.
.vtt cue times, EN+VI chapter times, README take minimums (24s/17s) and
spec-v7 scene table, no-overlap and dwell rules follow the new boundaries.
Re-rendered public/media/how-it-works.mp4.
2026-10-29 00:38:07 +07:00

20 lines
799 B
WebVTT

WEBVTT
00:00:00.000 --> 00:00:05.400
This site's CMS is a git repository.
00:00:05.500 --> 00:00:19.400
Everything the site shows is a JSON document: structure documents, per-language dictionaries and field manifests — joined once at build time.
00:00:19.500 --> 00:00:42.700
?edit turns the live site into the editor. HTTP Basic at the nginx proxy is the only gate; every save is a commit through the GitHub Contents API.
00:00:42.800 --> 00:00:56.700
Content lives as JSON in the repository: branches are previews, and merging to master publishes.
00:00:56.800 --> 00:01:13.700
Merging to master runs the GitHub Actions pipeline — build, resume PDFs, deploy — from commit to live in minutes.
00:01:13.800 --> 00:01:20.800
Edit on the live site. Stored in git. Live on merge to master.