The site fleet

Many display sites, one dashboard: catalogs, content, files, analytics.

Updated July 26, 2026

On this page

The shape

One operator, many brand or client sites — menu sites, catalog sites, local-presence sites. Grants: records, customers, websites, inventory, pages, media, contacts, , . Deliberately commerce: the inventory module shows products; it does not sell them.

insights

logs

not

The catalog

Products are product records with a draft → active gate — only active ever reaches a site. Variations (sizes, strains, flavors) with optional per-option prices and images; galleries from the files library.
Categories join by slug: lps.products.list({ category: "flower" }).
Scoping is per site with a shared pool — a fleet can share a master catalog and still give one site its own additions.

Content and files

Page copy and blog posts are content rows; site-specific rows beat shared ones, so a fleet-wide default can be overridden per site without forking anything.
Brand assets carry stable labels (home-hero) so a rebrand is a dashboard upload, not a fleet-wide code change.

Operating the fleet

Each site: its own keys, its own DO app (or its own hosting — the surface doesn't care), its own analytics, its own lead inbox.
The websites module is the fleet view: status, uptime, last deploy, cost per site.
The request trail answers "which site is hammering the API" by key and origin.

Why not a storefront organization?

If the sites need carts, checkout, taxes and shipping — that is the storefront system (organizations). The platform fleet pattern is for display: catalogs without commerce, content without a CMS to host, analytics without GA. Some businesses run both, and the two systems stay separate by design.