Skip to content

Content Delivery Overview

The Content Delivery module is the platform's configuration and content hub: themes, layouts, promotional blobs, and any presentation data the operator manages. Operators update content in their backoffice; your frontend fetches it dynamically; no redeploy required.

How content is structured

One platform rule governs all free-form data: the platform's structures are fully typed, and operator-supplied data rides inside typed envelopes as primitive/JSON passthrough; every value is a string, number, boolean, or JSON (never untyped holes). Content namespaces and blobs follow exactly that rule.

ConceptWhat it isWhere defined
NamespaceA named group of configuration values (e.g., theme, home_page)Dynamic Configuration
Content blobA larger typed payload (banner slider JSON, CSS block, file metadata)Dynamic Configuration
CachingIn-memory caching with an update-driven invalidation contractTheming, Caching & DOM Injection

Public surface

MemberReturnsAuthDescription
getAllNamespaces()Promise<string[]>publicEvery configured namespace
getConfig(namespace)Promise<ConfigNamespace>publicA namespace's configuration values
getContent(contentId)Promise<ContentBlob>publicA content blob by id
clearCache()voidnoneDrop all cached config/blobs (see caching)
applyThemeToDom(themeConfig)voidnoneApply a theme namespace as CSS variables (see theming)

Content reads are public; presentation and lobby data, like the games catalog. No session required.

Security note

Operator-supplied HTML and CSS blobs are delivered and rendered as-is. Sanitize content at the source (in the backoffice), and configure a Content-Security-Policy appropriate for your deployment; the SDK performs no sanitization.

Operator-configurable values

ValueTypeDefault / rangeEffect
Namespace catalog + contentsper namespaceoperator-definedWhich configs exist and what they contain
Content blob catalogper bloboperator-definedBanner data, CSS blocks, file metadata

The namespace/blob model, the typed value envelope, and the caching contract are platform-fixed.

See Environments & Sandbox Data for the seeded namespaces (theme, home_page).