Installable container
A package is a single installable boundary for one work and one edition.
BookField package format
wbpkg is the installable content package format that BookField imports for local-first reading, offline search, study plans, and structured references.
Version snapshot
At a glance
A wbpkg package contains one work and one edition. It carries the metadata, reader assets, navigation, optional schedules, and locator indexes needed for BookField to validate and install the package on the device.
A package is a single installable boundary for one work and one edition.
manifest.json defines identity, work, edition, assets, navigation, and optional entries.
ReaderDoc content is prepared for import, so the reader does not parse EPUB, HTML, or CSS at runtime.
navigationTree decides the entry point and the reader's package-level table of contents.
Locator indexes and bindings resolve authored references offline when matching packages are installed.
Authored study plans live in manifest.json only when the package includes schedule data.
Package layout
Package paths are package-root-relative POSIX paths. Text packages include ReaderDoc files under reader/, while image, audio, or video only packages may omit reader/ when they have no text asset.
manifest.json
reader/{assetId}/reader_manifest.json
reader/{assetId}/reader.rdoc
images/{assetId}.{ext}
images/{assetId}-thumb.{ext}
media/{assetId}.{ext}
locator/{profileId}.json
Manifest contract
manifest.json is the public contract that BookField reads before import. Legacy packageKind and presentation fields are not part of the current package shape.
Defines the package identity and package version used for install and replacement decisions.
Identifies the work and the edition contained by the package.
Lists text, image, audio, and video assets and the local paths that belong to each asset.
Defines the entry point and package navigation that the reader can open offline.
Adds authored schedules only when the package includes study plan metadata.
Connects authored references to locator indexes for offline resolution.
Package creation
Prepare source content, metadata, media, and any authored schedules or references.
Produce an installable package with manifest metadata, ReaderDoc content, media, navigation, and locator files.
Check the package structure and schema compatibility before distribution.
Reader import
BookField checks the package shape and rejects unsupported or malformed packages.
Supported package assets are unpacked into app-owned local storage.
ReaderDoc payloads, navigation, locator indexes, search records, and schedules are registered for offline use.
Compatibility
Canonical references
This public page is an implementation-facing overview, not the canonical schema source. The canonical docs and schema files live with the BookField source materials.
00-spec-index.md
Defines the version policy, shared manifest shape, package layout, path rules, study-plan storage, and locator policy that this page summarizes.
04-manifest-json-schema.md
Defines the manifest v5 contract, required navigationTree, package-root-relative paths, semantic validation boundary, and rejection rules.
08-reader-app-design.md
Defines how BookField validates, unpacks, imports ReaderDoc data into SQLite, and reads installed packages locally.
schemas/manifest-v5.schema.json / readerdoc-v3.schema.json
Provide the structural schemas for manifest.json and ReaderDoc payloads used by validation tooling.
When the canonical docs or schema files change, update the source first, then refresh this public snapshot and its explanation.
Return to the product overview, or discuss whether a wbpkg distribution flow fits your content model.