Lexicon Garden

pub.leaflet.content

Content format for leaflet documents

Repository @leaflet.pub did:plc:btxrwcaeyodrap5mnjw2fvmz namespace authority
Details · object
Kindobject
Authorityleaflet.pub
Indexed
Compare Edit in builder → Fork →

Object

object

Properties

blobPages

blob

JSON-encoded array of pages. When the inline pages array would be too large to store on the PDS, the pages are uploaded as a blob and referenced here. When set, consumers MUST ignore `pages` and use the decoded blob contents as the page array; the inline `pages` field will be empty or a stub.

  • maxSize: 5000000
  • accept: application/json

blobs

array

Blobs referenced inside `blobPages`. Load-bearing when `blobPages` is set: the PDS only scans the top level of a record for blob references when deciding what to garbage-collect, so any image/etc. blob now living inside the opaque JSON blob must be mirrored here to remain referenced.

itemsblob
  • maxSize: 10000000
  • accept: */*

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • pub.leaflet.document

    record

    A lexicon for long form rich media documents

  • blog.pckt.content

    object

    Hybrid content storage: inline for small content (≤20KB), blob for large content (>20KB)

  • com.pagehare.embeds

    record not from the namespace authority

    Structural blob retention sidecar for a site.standard.document. PDSs retain blobs only while a record field references them; image URLs inside the markdown string do not count. Every blob the document's markdown references must therefore also appear here. A pure derivation: regenerated from the document's content.markdown (plus upload metadata) on every write (rkey mirrors the document rkey), never hand-edited.

  • page.cavu.pages

    object not from the namespace authority

    Pre-paginated image content (comics, graphic novels, picture books, scanned pages) for a book chunk, carried in a site.standard.document record's `content` open union — the fixed-layout counterpart to a pub.leaflet.content text chunk. Each page is one image; readers lay pages into single-page or two-page-spread views using the book's pageProgression direction and each page's spread hint. The document's `textContent` field may carry a transcript or page descriptions for search and accessibility.