M3U8 lanes
Download, player, inspector, queue, and history now have dedicated workspace routes.
WorkspacePublic pages stay SEO-firstHero, why-use, FAQ, guides, blog bridges, and ad positions stay outside the execution shell. Workspace grows by laneFuture subtitle, video, and dev execution can add their own routes, queue, and history instead of extending one giant app. app.html becomes legacyOld links still work, but the execution center now lives under structured /workspace/ routes.
Execution lanes are now split from the public acquisition layer.
Use dedicated workspace routes for download, playback, inspection, queue, and operations. Keep SEO copy and lightweight acquisition on public pages.
Public vs workspace
Public pages explain and qualify. Workspace pages execute.
This split keeps the acquisition layer clean while giving execution, queue, and history a stable place to grow.
By group
Open the right execution lane first
Start from a product lane, not from one giant app shell.
Subtitle workspace
Subtitle execution now has dedicated workspace tool routes, so repeat-use conversion, sync, translation, and bilingual jobs no longer need to live only on public pages.
Video workspace
Video playback, clip planning, and share prep now have dedicated workspace tool routes, so video execution stops depending on one public surface or the old M3U8 shell.
Dev workspace
QA and compatibility helpers now have a first live dev lane, so browser-side manifest checks stop being buried inside generic tabs or planned placeholders.
Capability boundary
This lane is an execution overview. It does not promise playback or download success on its own.
- Use overview to choose the right next lane before running a task.
- Keep queue, history, and settings out of the public acquisition layer.
- Move into player, inspector, or downloader once the goal is clear.
Mobile execution
On narrow screens, keep the current task visible first and collapse helper rails into secondary controls.
- Player and inspector remain primary mobile modes.
- Queue, history, and settings should stay reachable without dominating the first screen.
- Avoid introducing extra fixed panels that cover inputs or results.
Storage contract
Saved playlists stay in Local Storage. TXT is the everyday import/export format and JSON remains the backup format.
- Playlist keys: m3u8-playlists, m3u8-recent-playlists.
- Settings key: m3u8-last-used-settings.
- Import TXT for routine work; use JSON only for backup and restore.
Low-interference sponsor slotView ad policy
Sponsor cards stay after the execution surface instead of cutting across the main input or primary action.
Slot IDad-ws-sponsor-primary-workspace-home
Placementsponsor-card
Modeself-promo
Densitylight