docs(media): add standalone package guide

2026-09-20 16:44:22 +08:00
parent c519d4e74b
commit eebf29c3d5
17 changed files with 326 additions and 78 deletions
@@ -1,34 +0,0 @@
---
-title: Media library
-description: Supply a storage adapter and add browsing, upload, folders, and asset selection.
-order: 21
-toc:
-  - id: implement-the-adapter
-    title: Implement the adapter
-  - id: provide-media
-    title: Provide media
-  - id: selection-flows
-    title: Selection flows
---
-
-## Implement the adapter {#implement-the-adapter}
-
-`MediaAdapter` is the media feature's complete persistence boundary. Implement its query, upload, folder, update, and delete operations with the product's storage service.
-
-## Provide media {#provide-media}
-
-Mount the adapter once around the media surfaces:
-
-```tsx
-import { MediaLibrary, MediaProvider } from "@workspace/blocks/media"
-
-;<MediaProvider adapter={mediaAdapter} notify={showNotice}>
-  <MediaLibrary />
-</MediaProvider>
-```
-
-The optional `notify` callback translates operational results into the application's toast or notification system.
-
-## Selection flows {#selection-flows}
-
-Use `MediaPickerDialog` for single or multiple asset selection. `readMediaDimensions`, `formatMediaFileSize`, and `defaultMediaReference` cover the common presentation work around uploads and previews.
@@ -33,7 +33,7 @@ Import the block stylesheet once from the application entry:
 import "@workspace/blocks/globals.css"
 ```

-Keep feature imports on their explicit subpaths. For example, importing `@workspace/blocks/media` does not pull chat into the same module graph.
+Keep feature imports on their explicit subpaths. For example, importing `@workspace/blocks/notifications` does not pull chat into the same module graph. Media workflows are provided separately by `@workspace/media`.

 ## Application providers {#application-providers}

@@ -13,7 +13,7 @@ toc:

 ## What you will build {#what-you-will-build}

-This tutorial builds an application shell step by step. You will begin with the shared layout, connect navigation, then add notifications, chat, media, and appearance preferences.
+This tutorial builds an application shell step by step. You will begin with the shared layout, connect navigation, then add notifications, chat, and appearance preferences.

 By the end, the application owns its data and business rules while `@workspace/blocks` owns the reusable presentation and interaction patterns.

@@ -29,5 +29,5 @@ Blocks sit above `@workspace/ui`. They combine low-level components into feature
 2. Create the application shell.
 3. Define navigation and route state.
 4. Connect notifications.
-5. Add chat and media workflows.
+5. Add chat workflows.
 6. Finish with persistent appearance controls.