docs(site): add "Why Video.js?" concept page#1526
Open
Conversation
New comprehensive concept page that answers "why a player library?" and "why this one?" Slotted between Installation and Overview in Getting started. Installation and Overview each get a one-line forward-link. https://claude.ai/code/session_01Uv795VrAR51b65fKTTn8gT
Installation: replace forward-link with a brief mini-pitch covering the same gaps Section A names. Why page: drop the artificial break and "Ready?" heading so the credibility paragraph flows as the last paragraph; correct Mux attribution to the four named teams only, with broader contributors mentioned separately. https://claude.ai/code/session_01Uv795VrAR51b65fKTTn8gT
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Deploy Preview for vjs10-site ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
📦 Bundle Size Report🎨 @videojs/html — no changesPresets (7)
Media (8)
Players (5)
Skins (30)
UI Components (34)
Sizes are marginal over the root entry point. ⚛️ @videojs/react — no changesPresets (7)
Media (7)
Skins (27)
UI Components (27)
Sizes are marginal over the root entry point. 🧩 @videojs/core — no changesEntries (9)
🏷️ @videojs/element — no changesEntries (2)
📦 @videojs/store — no changesEntries (3)
🔧 @videojs/utils — no changesEntries (10)
📦 @videojs/spf — no changesEntries (3)
ℹ️ How to interpretAll sizes are standalone totals (minified + brotli).
Run |
- Consolidate the two-paragraph install intro into one - Soften HLS browser-support phrasing to "not every browser" - Rename pillar #1 from "Pay only for what you use" to "Add only what you need" - Switch pillar #4's HLS swap from a diff marker to a focus marker - Use the canonical stream.mux.com asset in pillar #4 - Add an "About v10" H2 above the closing paragraph - Drop the install CTA card; sidebar prev/next already covers it https://claude.ai/code/session_01Uv795VrAR51b65fKTTn8gT
sampotts
reviewed
May 7, 2026
|
|
||
| ### Framework-native | ||
|
|
||
| Many player libraries wrap a single web component for every framework. That works, until you reach the seams: refs you can't pass through, state that doesn't reconcile, prop names that aren't quite React or HTML. Video.js v10 ships idiomatic APIs in each framework: React components and hooks for React, custom elements and controllers for HTML. The player feels like the rest of your app. |
Collaborator
There was a problem hiding this comment.
Is it worth mentioning something about the architecture lending itself to supporting more frameworks in future too?
Collaborator
Author
There was a problem hiding this comment.
Yes totally. Good suggestion.
sampotts
approved these changes
May 7, 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
3 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.
Closes #1059.
Summary
site/src/content/docs/concepts/why-videojs.mdxanswering "why use a player library?" then "why this one?"Page shape
Drawn from the planning thread on #1059, the v10 beta blog post, and the four Mux author posts. Roughly 1100 words.
Header.astroH1 andBuilt/Intro.astro<video>(streaming formats, inconsistent/unstylable controls, multi-source playback). Prose only; no comparison tableTest plan
/docs/framework/html/concepts/why-videojs/and/docs/framework/react/concepts/why-videojs/<DocsLink>and<DocsLinkCard>slugs resolve (concepts/features,how-to/customize-skins,concepts/accessibility,how-to/build-with-ai)installation.mdxand the new line onoverview.mdxlink correctly<video>tag references render as inline code, not as actual elementsValidation run locally
pnpm test— 381 passingpnpm astro check— 0 errors afterpnpm build:packagespnpm check:workspacepnpm lint:fix:fileon touched fileshttps://claude.ai/code/session_01Uv795VrAR51b65fKTTn8gT
Note
Low Risk
Low risk: documentation-only changes plus a sidebar entry; main failure modes are broken links or rendering issues in the new MDX content/tabs.
Overview
Adds a new docs concept page,
concepts/why-videojs, explaining when to use a player library and the design pillars of Video.js v10, including React/HTML examples and cross-links to related docs.Wires the new page into the Getting started sidebar (between Installation and Overview) and adds forward-links from
how-to/installation.mdxandconcepts/overview.mdxto point readers to the new rationale page.Reviewed by Cursor Bugbot for commit 503e133. Bugbot is set up for automated code reviews on this repo. Configure here.