Fix introduction hero video: serve from S3, drop 66MB mp4#26
Merged
Conversation
The video was committed as a 66MB 1080p/11.5Mbps mp4 and embedded via <Frame> with a <source> child. A file that large won't reliably serve through Mintlify (past GitHub's 50MB warning), so the player showed nothing. - Re-encode to H.264 1080p ~1Mbps + faststart (66MB -> 5.7MB, no visible quality loss) and host on the public fluso-docs-assets S3 bucket. - Embed with a plain Mintlify <video> tag (className sizing, muted, playsInline, preload=metadata) pointing at the S3 URL. - Remove the binary from git and gitignore *.mp4/*.mov/*.webm so large media stays out of source control.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
biswaroop1547
approved these changes
Jul 2, 2026
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
2 participants
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.
Problem
The introduction hero video (added in #23) didn't play. It was committed as a 66MB, 1080p / 11.5 Mbps
.mp4inside the repo and embedded via<Frame>with a<source>child. A binary that large is past GitHub's 50MB warning and won't reliably serve through Mintlify, so the player rendered nothing. The original also lackedfaststart, which makes browsers wait for the full download before playing.Fix
+faststart→ 66MB → 5.7MB, no visible quality loss.fluso-docs-assetsbucket (us-east-1) atintroduction/fluso-brand-video-v7.mp4withContent-Type: video/mp4and a 1-year immutable cache header. Verified200+Accept-Ranges: bytes+ range requests return206(seeking works).<video>tag (their documented pattern) pointing at the S3 URL; dropped the<Frame>wrapper (that's the image component).*.mp4/*.mov/*.webmto.gitignoreso large media stays out of source control.URL:
https://fluso-docs-assets.s3.us-east-1.amazonaws.com/introduction/fluso-brand-video-v7.mp4Note: the bucket serves directly from S3 (no CloudFront). Fine for a single small file; edge caching / a branded domain can be added later.
🤖 Generated with Claude Code