Skip to content

Build themes

A theme controls how a public storefront looks and renders. Themes are written in Liquid. Designers publish public themes to the Stayblox marketplace with the Stayblox CLI; hosts who want a bespoke look can instead upload a .zip as a private custom theme for their own storefront.

Building an integration instead? That is a different surface. Build apps

How a storefront renders a theme

 You (author)
     │  stayblox theme push  (CLI: draft → review → approved)
     │  …or upload a .zip in the admin (private custom theme)

 Theme (marketplace catalog)  ──versioned──▶  ThemeVersion  ──contains──▶  files
     │  host installs

 Site theme (per site)  ──stores──▶  settings + edited-file overrides
     │  one is marked active

 Storefront request ──▶ active theme's templates render via Liquid
  • You author a theme; published versions live in the marketplace catalog as versioned, immutable file sets.
  • A host installs it: Stayblox seeds a per-site settings record and pins the install to that version. Files the host edits become site-level overrides; everything else keeps resolving to your published files.
  • On each storefront request, the active theme's templates are resolved and rendered by Liquid. Host edits and settings never affect the marketplace original.

Two ways to publish

PathForHow
MarketplaceDesigners selling public themesCLI: validatepush (private draft) → submit → review → approved
Custom themeHosts skinning their own storefrontUpload a .zip in the admin. No review, private to your site.

What you work with

  • Templates in Liquid, over a data model that's just the storefront GraphQL schema, plus a fixed set of filters and tags.
  • Settings you declare so hosts can customise the theme without code.
  • Assets (CSS and JS today) served from a stable URL.

Where to go next

© Stayblox — Developer Platform