The template is configured by a single typed file, site.config.ts. It ships as a complete reference — every option is present, the unused ones commented out with their defaults — so configuring is mostly uncommenting. A typo or wrong value fails the build with a readable message before anything deploys.
The blocks
- site — name, logo, absolute URL (canonical tags + sitemap), description, language, and
noindexfor staging deploys. - event — the Cloomba event slug this site renders. One event per site; a satellite event is a second deployment.
- theme —
mode(autofollows the visitor's system with a toggle;light/darkpin one), font stacks, corner radius, and the color tokens per mode:primary,primary_content,accent,surface,surface_alt,text,text_muted. Set any subset — the rest keep sensible defaults. - sections — the home page as a list: order is display order, removing a line removes the section. Fourteen block types, from
heroandstatstofaqand the closingcta. - header / footer — omit them and navigation derives itself from the enabled sections and your custom pages; set them to take full control. The footer also carries app links and privacy/terms URLs.
- socials — profile URLs; icons are detected from the domain automatically.
- analytics — a self-hosted Umami script (cookieless — no consent banner needed), plus
head_htmlfor anything else: Google Analytics, a Meta pixel, any snippet, injected verbatim into<head>. Cookie-based trackers make you responsible for a consent banner — the template ships none. - cloomba_promo — the "built with Cloomba" band above the footer. Set
falseto hide it.
Secrets live in .env, not in the config
The committed config holds production endpoints only. Your API key — and any local-development overrides — go in .env (gitignored; see .env.example):
CLOOMBA_API_KEY— a free read-only key from cloomba.com/me/developers. Build-time only; it never reaches the browser.CLOOMBA_API_URL,CLOOMBA_BROWSER_API_URL,CLOOMBA_EMBED_ORIGIN— optional overrides for developing against a non-production Cloomba.