@videojs/html 10.0.0-beta.23 → 10.0.0-beta.24

package/docs/concepts/features.md

@@ -0,0 +1,129 @@
+# Features
+
+The state and actions each feature adds to the player
+
+Not every player needs to support every use case. To address this, Video.js has a concept of **features** — self-contained units of player functionality. Each one adds state properties and actions to the player. For example, “playback” adds `paused` and `play()`, “volume” adds `volume` and `setVolume()`, and so on.
+
+## Using features
+
+### Feature bundles and presets
+
+You probably don’t want to hand-pick every feature your player needs. A **feature bundle** groups the features needed for a specific use case into a single array.
+
+For example, if you import `<video-player>` from the `/video` path, you will have playback, volume, time, fullscreen, and more already enabled.
+
+html
+
+```
+<script type="module" src="@videojs/html/video/player"></script>
+<video-player>
+  <video-skin>
+    <video src="movie.mp4"></video>
+  </video-skin>
+</video-player>
+```
+
+Feature bundles are usually paired with specific skins and media elements in a **preset** . To learn more about this, and the available presets, you’ll want to check out the presets guide.
+
+[Learn more about presets](./presets.md)
+
+### Create a player with individual features
+
+If you’re not using presets, you can create a player that has individual features.
+
+ts
+
+```
+import { createPlayer, playbackFeature, volumeFeature, timeFeature, controlsFeature } from '@videojs/html';
+
+const { ProviderMixin, PlayerController, context } = createPlayer({
+  features: [playbackFeature, volumeFeature, timeFeature, controlsFeature],
+});
+
+class MyPlayer extends ProviderMixin(MediaElement) {
+  static readonly tagName = 'my-player';
+}
+
+customElements.define('my-player', MyPlayer);
+```
+
+### Extending a feature bundle
+
+Since feature bundles are just an array of features under the hood, it doesn’t take much to extend one. For example, if you were using the `/background` preset and wanted a play button on your background video, you might add the playback feature.
+
+ts
+
+```
+import { createPlayer, playbackFeature } from '@videojs/html';
+import { backgroundFeatures } from '@videojs/html/background';
+import { MediaElement } from '@videojs/html';
+
+const { ProviderMixin } = createPlayer({
+  features: [...backgroundFeatures, playbackFeature],
+});
+
+class MyPlayer extends ProviderMixin(MediaElement) {
+  static readonly tagName = 'my-player';
+}
+
+customElements.define('my-player', MyPlayer);
+```
+
+### Access features in components
+
+You can access feature state and actions through [`PlayerController`](../reference/player-controller.md) and pre-built feature selectors (e.g. [`selectPlayback`](../reference/feature-playback.md), [`selectVolume`](../reference/feature-volume.md)):
+
+ts
+
+```
+import { selectPlayback } from '@videojs/html';
+
+// Subscribe to feature state (triggers element updates on change)
+readonly #playback = new PlayerController(this, context, selectPlayback);
+
+// Read state and call actions
+const media = this.#playback.value;
+if (media?.paused) media.play();
+```
+
+### Checking for feature support
+
+Volume, fullscreen, and picture-in-picture expose an `*Availability` property because platform support varies. For example, iOS Safari doesn’t allow programmatic volume control.
+
+Value
+
+Meaning
+
+`'available'`
+
+Ready to use
+
+`'unavailable'`
+
+Could work, not ready yet
+
+`'unsupported'`
+
+Platform can never do this
+
+Components that depend on availability (like [`PiPButton`](../reference/pip-button.md) and [`FullscreenButton`](../reference/fullscreen-button.md)) expose a `data-availability` attribute, so you can hide unsupported controls with CSS:
+
+css
+
+```
+media-pip-button[data-availability="unsupported"] {
+  display: none;
+}
+```
+
+You can also check availability in JS:
+
+ts
+
+```
+const media = this.#pip.value;
+
+if (media?.availability === 'unsupported') {
+  this.hidden = true;
+}
+```

package/docs/concepts/overview.md

@@ -0,0 +1,118 @@
+# Overview
+
+How Video.js players are structured — state, UI, and media
+
+Video.js v10 is built around a three-part architecture that separates concerns and maximizes flexibility. Each part is designed to work independently or together, allowing you to use as much or as little of Video.js as you need.
+
+For the reasoning behind this design, see [Why Video.js?](./why-videojs.md).
+
+## 1\. State management
+
+State is handled by a `video-player` element, which creates a central state store that all components can access. Child components can automatically connect to the state of the `video-player` element.
+
+html
+
+```
+<!-- All components inside automatically connect to state -->
+<video-player>
+  <video-skin>
+    <video src="video.mp4"></video>
+  </video-skin>
+</video-player>
+```
+
+You can access state and actions from anywhere within `<video-player>` with [`PlayerController`](../reference/player-controller.md).
+
+[Learn more about state and actions](./features.md)
+
+## 2\. User interface
+
+Use a prebuilt **skin** or build your own from the individual **UI components** .
+
+### Skins
+
+Skins are complete, pre-designed player UIs that package components and styles together:
+
+html
+
+```
+<video-player>
+  <video-skin>
+    <video src="video.mp4"></video>
+  </video-skin>
+</video-player>
+```
+
+[Learn more about skins](./skins.md)
+
+### UI components
+
+If you want more control than skins offer you, you can build your own UI from our components.
+
+html
+
+```
+<video-player>
+  <media-container>
+    <video src="video.mp4"></video>
+    <media-controls>
+      <media-play-button></media-play-button>
+      <!-- ... -->
+    </media-controls>
+  </media-container>
+</video-player>
+```
+
+To get started with UI components, you might consider [ejecting a skin](../how-to/customize-skins.md) and using its pre-styled components as a foundation.
+
+[Learn more about UI components](./ui-components.md)
+
+[Build your own component](../how-to/build-your-own-component.md)
+
+## 3\. Media
+
+Media components are the components that actually display your media. They’re essentially “players with no UI”. They handle the video/audio rendering and expose a consistent API.
+
+Media components can be format specific (HLS, DASH), service specific (YouTube, Vimeo, Mux), or use case specific (background video).
+
+Media elements are discovered automatically. Plain `<video>` and `<audio>` elements are found via a `querySelector`, while custom media elements like `<hls-video>` register themselves.
+
+Note
+
+DASH, YouTube, Vimeo, Mux, and more media elements are currently under development.
+
+html
+
+```
+<video-player>
+  <video-skin>
+    <hls-video src="https://stream.mux.com/BV3YZtogl89mg9VcNBhhnHm02Y34zI1nlMuMQfAbl3dM.m3u8"></hls-video>
+  </video-skin>
+</video-player>
+```
+
+## Presets
+
+**Presets** preconfigure these parts for a specific use case.
+
+The default presets are `@videojs/html/video` and `@videojs/html/audio`, covering the baseline set of controls you’d expect from the HTML `<video>` and `<audio>` tags.
+
+Beyond the defaults, presets target more specific use cases. For example, `/background` includes a media element with autoplay, mute, and loop built in, a skin with no controls, and just the features needed to power it:
+
+html
+
+```
+<script type="module">
+  import '@videojs/html/background/player';
+  import '@videojs/html/background/video';
+  import '@videojs/html/background/skin';
+</script>
+
+<background-video-player>
+  <background-video-skin>
+    <background-video src="hero.mp4"></background-video>
+  </background-video-skin>
+</background-video-player>
+```
+
+[Learn more about presets](./presets.md)

package/docs/concepts/presets.md

@@ -0,0 +1,207 @@
+# Presets
+
+Pre-packaged player configurations that bundle state management, skins, and media elements for specific use cases.
+
+A **preset** packages what you need for a specific player use case. It can include special [state management](./features.md), one or more [skins](./skins.md) for UI, and specific media elements. Instead of assembling these pieces individually, you pick a preset that matches what you’re building.
+
+For example, the `@videojs/html/background` preset includes a media element with autoplay, mute, and loop built in, a skin with no controls, and just the features needed to power them:
+
+index.html
+
+```
+<script type="module">
+  import '@videojs/html/background/player';
+  import '@videojs/html/background/video';
+  import '@videojs/html/background/skin';
+</script>
+
+<background-video-player>
+  <background-video-skin>
+    <background-video src="hero.mp4"></background-video>
+  </background-video-skin>
+</background-video-player>
+```
+
+## Available presets
+
+The default presets are `/video` and `/audio`. These cover the baseline controls you’d expect from the HTML `<video>` and `<audio>` tags. Beyond the defaults, presets target more specific use cases — the `/background` preset, for example, needs layout but not controls. Over time we’ll add more: short-form players, podcast players, TV streaming players, and others.
+
+Import
+
+Description
+
+Details
+
+`@videojs/html/video`
+
+General-purpose video player preset with full playback controls.
+
+▸
+
+Feature bundle
+
+`videoFeatures`
+
+Features
+
+[playback](../reference/feature-playback.md), [playbackRate](../reference/feature-playback-rate.md), [volume](../reference/feature-volume.md), [time](../reference/feature-time.md), [source](../reference/feature-source.md), [buffer](../reference/feature-buffer.md), [fullscreen](../reference/feature-fullscreen.md), [pip](../reference/feature-pip.md), [remotePlayback](../reference/feature-remote-playback.md), [controls](../reference/feature-controls.md), [textTrack](../reference/feature-text-tracks.md), [error](../reference/feature-error.md)
+
+Skins
+
+`<video-minimal-skin>`, `<video-skin>`
+
+Default media element
+
+`<video>`
+
+`@videojs/html/audio`
+
+Audio-only player preset with playback and volume controls.
+
+▸
+
+Feature bundle
+
+`audioFeatures`
+
+Features
+
+[playback](../reference/feature-playback.md), [playbackRate](../reference/feature-playback-rate.md), [volume](../reference/feature-volume.md), [time](../reference/feature-time.md), [source](../reference/feature-source.md), [buffer](../reference/feature-buffer.md), [error](../reference/feature-error.md)
+
+Skins
+
+`<audio-minimal-skin>`, `<audio-skin>`
+
+Default media element
+
+`<audio>`
+
+`@videojs/html/background`
+
+Ambient background video preset with no user controls.
+
+▸
+
+Feature bundle
+
+`backgroundFeatures`
+
+Features
+
+–
+
+Skins
+
+`<background-video-skin>`
+
+Default media element
+
+`<background-video>`
+
+`@videojs/html/live-audio`
+
+Live audio player preset — same features as `audio` with a skin that omits duration / current-time displays.
+
+▸
+
+Feature bundle
+
+`liveAudioFeatures`
+
+Features
+
+[playback](../reference/feature-playback.md), [volume](../reference/feature-volume.md), [time](../reference/feature-time.md), [source](../reference/feature-source.md), [buffer](../reference/feature-buffer.md), [error](../reference/feature-error.md), [live](../reference/feature-live.md)
+
+Skins
+
+`<live-audio-minimal-skin>`, `<live-audio-skin>`
+
+Default media element
+
+–
+
+`@videojs/html/live-video`
+
+Live video player preset — same features as `video` with a skin that omits duration / current-time displays.
+
+▸
+
+Feature bundle
+
+`liveVideoFeatures`
+
+Features
+
+[playback](../reference/feature-playback.md), [volume](../reference/feature-volume.md), [time](../reference/feature-time.md), [source](../reference/feature-source.md), [buffer](../reference/feature-buffer.md), [fullscreen](../reference/feature-fullscreen.md), [pip](../reference/feature-pip.md), [remotePlayback](../reference/feature-remote-playback.md), [controls](../reference/feature-controls.md), [textTrack](../reference/feature-text-tracks.md), [error](../reference/feature-error.md), [live](../reference/feature-live.md)
+
+Skins
+
+`<live-video-minimal-skin>`, `<live-video-skin>`
+
+Default media element
+
+–
+
+## What’s in a preset
+
+Each preset exports up to three things:
+
+*   **Feature bundle** — An array of [features](./features.md) that define the player’s state and actions. For example, the video feature bundle includes playback, volume, time, fullscreen, and more.
+*   **Skins** — Pre-built UIs designed for that feature bundle. For example, a video skin renders fullscreen and PiP controls because the video feature bundle includes those features. An audio skin doesn’t.
+*   **Media element** — A media component suited to the use case. For example, the background video element bakes in autoplay, mute, and loop.
+
+These parts aren’t equally tied together. Skins depend tightly on their feature bundle — a skin expects specific features to exist. Media elements are more interchangeable — you can swap in an HLS or DASH provider without changing your skin or features.
+
+## Customizing a preset
+
+You can customize a preset in three ways: extend its feature bundle, eject its skin, or swap its media element.
+
+### Extend the feature bundle
+
+Add features to a preset’s feature bundle to enable new functionality. For example, adding playback controls to a background video:
+
+index.html
+
+```
+<script type="module">
+  import { createPlayer, playbackFeature, MediaElement } from '@videojs/html';
+  import { backgroundFeatures } from '@videojs/html/background';
+  import '@videojs/html/media/container';
+  import '@videojs/html/ui/play-button';
+
+  const { ProviderMixin } = createPlayer({
+    features: [...backgroundFeatures, playbackFeature],
+  });
+
+  class MyPlayer extends ProviderMixin(MediaElement) {
+    static readonly tagName = 'my-player';
+  }
+
+  customElements.define('my-player', MyPlayer);
+</script>
+
+<my-player>
+  <media-container>
+    <background-video src="hero.mp4"></background-video>
+    <media-play-button>Play / Pause</media-play-button>
+  </media-container>
+</my-player>
+```
+
+### Eject the skin
+
+If a preset’s skin is close but not quite right, you can [eject it](../how-to/customize-skins.md) — copy its internal components into your project and customize from there.
+
+### Swap the media element
+
+A preset’s default media element is just the starting point. You can replace it with any compatible media provider. For example, using an HLS source with the video preset:
+
+html
+
+```
+<video-player>
+  <video-skin>
+    <hls-video src="https://example.com/stream.m3u8"></hls-video>
+  </video-skin>
+</video-player>
+```