Add click-to-play homepage launch video - #53
Merged
Conversation
Preserve current marketing layout and canonical templates; adopt exact optimized media, native progressive controls, scoped range/cache delivery and regression coverage. Co-Authored-By: CRHQ <noreply@crhq.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Approved scope
docs/homepage-video.md.Verification
pnpm check+ typecheck/build pass:41 exact existing warning locations/rules, no added warnings/errors.Limits / rollout
Chromium lab evidence, not Safari/iPhone/Firefox/deployed-CDN certification. No perceptual audio audition was available; objective audio alignment/decode checks are not listening. Small embedded text may need native fullscreen/transcript. Player activation CLS0 is separate from initial font swaps in the existing shell; no global-zero claim.
Review only: do not merge/deploy yet. Existing guarded deployment provides assets-before-page ordering. No homepage-status flip. Planned rollback is scoped code revert with immutable media retained for already-served references, then the same guarded deploy; no routine DB restore. No icon adoption or unrelated changes.