docs(dash): [SITE-DASH-01] add bilingual guides and fix example lifecycle

This commit is contained in:
Harvey Zhao committed 2026-09-15 18:09:30 +08:00
1 parent 4ea0ba94ae
commit 319dccb605
70 files changed
+4005 -1695

No files matched your search

@@ -148,6 +148,20 @@ and checked standalone against both TS 4.3.5 and 5.9.3, then consumed by real Mo
## Validation and next work
The bilingual `artplayer-vitepress/docs/{en/,}plugin/dash-control.md` guides contain
the exact `docs/assets/example/dash.control.js` setup. The example keeps one final
SDK cleanup listener, releases replaced instances once, skips SDK-dependent controls
when MediaSource is unsupported, and formats nullable language metadata safely.
`test/dash-example.test.js` exercises the actual source against these old failures.
`document-dash.spec.js` requires both guides to match that source, then runs it with
both frozen SDK generations and published/candidate core. WebKit's unsupported
branch is capability evidence only. The original SDK initialization settings and
plugin APIs are unchanged; full SDK/device/DRM acceptance remains separate.
When changing the example, update both guides, run the example and browser tests,
rebuild the LLM corpus/docs and refresh the site inventory. `document-site.spec.js`
checks guide navigation and the two-library Run Code parameters in both languages.
Run at the workspace root with pinned Node and Yarn:
```sh
@@ -2,6 +2,11 @@
Dash control plugin for ArtPlayer
Complete usage and SDK ownership:
[English guide](../artplayer-vitepress/docs/en/plugin/dash-control.md) /
[中文指南](../artplayer-vitepress/docs/plugin/dash-control.md).
These guides describe the current refactor branch; its fixes are not published yet.
Accepts a caller-owned dash.js instance at `art.dash`. Quality selection adapts to the
dash.js 4.x quality methods or 5.x representation methods. Version 5 selection uses
representation IDs so bitrate filtering does not change the selected quality.