vyla-entertainment/documentation
2
0
Fork 0
mirror of https://gitlab.com/vyla-entertainment/documentation.git synced 2026-11-14 14:37:25 -05:00
Code Issues Packages Projects Releases Wiki Activity

added manga integration

Browse Source
This commit is contained in:
alwaysmesmerizingyou
2026-10-14 21:55:45 -07:00
parent 401a16d07d
commit b42f21f48a
6 changed files with 320 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
start-here/architecture.md
View File

@@ -12,7 +12,7 @@ Home is responsible for a desktop session: local configuration, encrypted local
### Vyla SDK
The SDK contains the provider-facing work: source configuration, stream resolution, subtitle retrieval, download lookup, and health probes. It is the right layer when your Node.js application needs to decide how requests are authorized, cached, selected, and returned.
The SDK contains the provider-facing work: source configuration, stream resolution, subtitle retrieval, manga discovery and page resolution, download lookup, and health probes. It is the right layer when your Node.js application needs to decide how requests are authorized, cached, selected, and returned.
### Stream API
@@ -35,4 +35,10 @@ Stream API wraps the SDK in a self-hosted HTTP service. Its movie and TV endpoin
4. The player begins with the first compatible candidate and keeps later candidates as fallbacks.
5. Subtitle and download lookups are separate operations; neither should block first playback.
Provider availability varies by source and network environment. Build the player experience around fallbacks and empty-result states, as described in [Error handling](/guides/error-handling).
Provider availability varies by source and network environment. Build the player experience around fallbacks and empty-result states, as described in [Error handling](/guides/error-handling).
## Data flow for manga
1. A client provides a search term, or direct manga identifier.
2. The SDK queries the manga provider for title details, metadata, and chapter listings.
3. When reading a chapter, the SDK resolves ordered page assets with dimensions and aspect ratios for responsive layout rendering.