Which documentation could use some work?
Is this a discrepancy or an improvement?
🖊 Describe what you'd like to see change in the documentation
The skins concept page lists React skins (VideoSkin, MinimalVideoSkin, AudioSkin, MinimalAudioSkin, …) in the preset reference table, but does not show which CSS file each one requires.
For example, MinimalVideoSkin needs:
import '@videojs/react/video/minimal-skin.css';
Without that import the player renders unstyled with no console warning or visual fallback — a confusing first-run failure mode for anyone switching between the default and minimal variants.
💡 Describe how you think this change will help the documentation
Show the required CSS import path next to each React skin name in the preset reference table. Users currently have no way to discover the correct import path without digging into the package internals or trial and error. Note: HTML auto-imports its CSS, so this is React-only.
Which documentation could use some work?
Is this a discrepancy or an improvement?
🖊 Describe what you'd like to see change in the documentation
The skins concept page lists React skins (
VideoSkin,MinimalVideoSkin,AudioSkin,MinimalAudioSkin, …) in the preset reference table, but does not show which CSS file each one requires.For example,
MinimalVideoSkinneeds:Without that import the player renders unstyled with no console warning or visual fallback — a confusing first-run failure mode for anyone switching between the default and minimal variants.
💡 Describe how you think this change will help the documentation
Show the required CSS import path next to each React skin name in the preset reference table. Users currently have no way to discover the correct import path without digging into the package internals or trial and error. Note: HTML auto-imports its CSS, so this is React-only.