Skip to content

docs(readme): inline GIF preview + YouTube link for the full tour#49

Merged
sathyaprakash000 merged 1 commit into
mainfrom
docs/gif-inline-plus-youtube
May 26, 2026
Merged

docs(readme): inline GIF preview + YouTube link for the full tour#49
sathyaprakash000 merged 1 commit into
mainfrom
docs/gif-inline-plus-youtube

Conversation

@sathyaprakash000
Copy link
Copy Markdown
Contributor

Why

The previous video PRs (#46, #47) shipped a <video src=...> element, but GitHub's README sanitizer strips <video> elements whose src isn't on its allowlist — and only user-attachments/assets/* URLs are on that list. Release-asset URLs and raw.githubusercontent.com URLs both get scrubbed. Net result: visitors saw only the fallback caption, no video element.

What changed

Switch the inline preview from <video> (sanitized away) to an animated <img> GIF — github.com trusts <img> from any raw/relative URL.

-<p align="center">
-  <video controls width="720" preload="metadata"
-         src="https://raw.githubusercontent.com/.../forgechat-overview.mp4"
-         poster="https://img.youtube.com/vi/tvYR0cGOj_4/maxresdefault.jpg">
-    <a href="https://youtu.be/tvYR0cGOj_4">fallback…</a>
-  </video>
-</p>
-<p align="center"><sub>▶ Video tour — also on YouTube if the embed doesn't play.</sub></p>
+<p align="center">
+  <a href="https://youtu.be/tvYR0cGOj_4"><img src="docs/forgechat-overview.gif" alt="ForgeChat video tour" width="720" /></a>
+</p>
+<p align="center"><sub>▶ Video tour (above, no audio) — <a href="https://youtu.be/tvYR0cGOj_4">watch the full version on YouTube</a> with narration.</sub></p>

Wrapping the GIF in <a href="https://youtu.be/..."> means clicking the GIF opens the full audio version on YouTube — best of both worlds.

Files

  • Added docs/forgechat-overview.gif — 14 MB, 640×310, 12 fps, palette-optimized via ffmpeg's two-pass palettegen + bayer dither. Visually equivalent to the MP4 for a screen-recording tour.
  • Removed docs/forgechat-overview.mp4 from the working tree. The same MP4 stays attached to the v1.0.0 release for direct download. (Git history still holds the blob; this only shrinks the working-tree size for new clones.)
3 files changed, 2 insertions(+), 4 deletions(-)
docs/forgechat-overview.gif | Bin 0 -> 13953789 bytes
docs/forgechat-overview.mp4 | Bin 32107461 -> 0 bytes

Test plan

  • CI green
  • Open README on github.com in incognito → the GIF auto-plays inline under the badges
  • Click the GIF → opens https://youtu.be/tvYR0cGOj_4 in a new tab

GitHub's README sanitizer strips <video src=...> elements whose src
isn't on the user-attachments allowlist — even when the URL is a
trusted github.com/.../raw or raw.githubusercontent.com path. That
left the previous embed (#46, #47) rendering as just the fallback
caption.

Fix: switch the inline preview to an animated GIF (<img>), which
github.com's sanitizer trusts from any raw/relative URL and which
auto-plays / auto-loops on scroll-into-view in every markdown
renderer (web, GitHub mobile, IDE previews). Keep the YouTube link
right under it for viewers who want audio + full quality.

Files
- Add docs/forgechat-overview.gif — 14 MB, 640×310, 12 fps, palette-
  optimized with bayer dither. Visually equivalent to the MP4 for a
  screen-recording tour.
- Remove docs/forgechat-overview.mp4 from the working tree. The same
  MP4 stays attached to the v1.0.0 release for direct download. Git
  history still holds the blob (added in #47), so this only shrinks
  the working-tree size for clones from main forward.
- README block becomes <img> wrapped in <a href=YouTube>, with a
  caption below pointing at YouTube for the full audio version.

Signed-off-by: KingArthur000 <sathyaprakashelango@gmail.com>
@sathyaprakash000 sathyaprakash000 merged commit b5c4042 into main May 26, 2026
11 checks passed
@sathyaprakash000 sathyaprakash000 deleted the docs/gif-inline-plus-youtube branch May 26, 2026 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant