Minisites — Data Model

minisite_content

Defined in libs/db/src/lib/schema/minisites.ts. One row per organization (unique on organization_id).

Relations

• minisite_content ↔ organizations one-to-one. Deleting an org cascades the minisite row via the FK.

minisite_events

Defined in libs/db/src/lib/schema/minisites.ts; created by migration libs/db/drizzle/0066_lying_siren.sql. Dated, promotable events/workshops for an org. Many rows per org. Events are NOT purchasable; registration is lead-capture only (the CTA points at the contact page/section), so there is no payment/entitlement coupling.

• Index minisite_events_org_idx on (organization_id, starts_at).
• The resolve endpoint surfaces upcoming published rows in platformData.events[]; the editor manages them via the events CRUD endpoints.

Live data (not persisted in this module)

The platformData payload composed by the resolve endpoint pulls from existing tables:

events is the one platform-data source authored inside the minisites module (the minisite_events table below); the rest are external tables. No copy of these lives in minisite_content.content, so the minisite always sees fresh data.

Pricing DTO extensions (FIT-287)

Each element of platformData.plans[] carries the pre-existing 8 fields (id, name, description, type, priceInCents, currency, interval, classCredits) plus five optional fields. These were once gated on a plan-intro-pricing PostHog flag; that flag was removed (2026-08-19) and the fields are now emitted for every org. They stay optional because each is absent on its own terms — absent from the JSON entirely, not merely null:

Internal-only derived fields (seatsTaken, capScope, maxPurchases, planGroupId) never reach this public DTO.

Per-group show_cap_to_members (FIT-289). plan_groups.show_cap_to_members (boolean NOT NULL DEFAULT true) is an owner toggle on the group. The minisite resolves seats for a member audience (computeSeatFields(..., 'member')), so when a plan’s binding cap is a group with the toggle off, the DTO emits soldOut and omits seatsLeft — the two are emitted independently for exactly this reason. Consumers must key buyability off soldOut, never off whether seatsLeft is present. Staff-facing payloads (PlansService, dashboard) are unaffected and always carry the full seat set.

platformData also gains a top-level optional joinUrl: string | null (FIT-287) — the org’s public join link (${FRONTEND_URL}/join/${org.joinToken}), present only when the full purchase-CTA gate passes: minisite-plan-purchase flag on, org.joinEnabled with a token, published pricing section isEnabled with ctaMode: 'purchase', and an active payment config. See behavior.md § Pricing and purchase CTA for the full rule and rendering.

Both extensions are additive to the shared type MinisitePlatformData (libs/shared/src/lib/minisite.ts) — old published payloads and flag-off orgs parse unchanged.

Indexes & uniqueness

• custom_domain and subdomain are independently unique to support either resolution path.
• Lookup happens by host header at request time — both columns are read; performance relies on the unique indexes.

Content shape (informal)

Authoritative Zod schemas live in libs/shared/src/lib/minisite.ts (MinisiteContent, MinisitePage, MinisiteSection, MinisiteTheme).

type Section = {
  type: 'hero' | 'about' | 'classes' | 'schedule' | 'pricing'
      | 'courses' | 'trainers' | 'contact' | 'gallery'
      | 'testimonials' | 'faq' | 'social' | 'events';
  order: number;
  isEnabled: boolean;
  data: Record<string, unknown>; // section-specific payload
};
 
type Page = {
  kind: 'home' | 'courses' | 'workshops' | 'about' | 'contact';
  slug: string;        // '' for home; mirrors PAGE_SLUGS[kind]
  navLabel: string;
  isEnabled: boolean;  // page renders + can appear in nav
  showInNav: boolean;  // surface in top nav (home often hidden)
  order: number;
  sections: Section[];
};
 
type MinisiteContent = {
  title?: string;
  locale?: 'he' | 'en' | 'ru';
  theme?: {
    primaryColor?: string;       // default copper #b86a35
    secondaryColor?: string;     // default cream #f4efe7
    fontFamily?: string;
    headingFontFamily?: string;  // optional separate display font
    buttonStyle?: 'rounded' | 'pill' | 'square';
    cornerStyle?: 'sharp' | 'soft' | 'round';
    sectionDensity?: 'compact' | 'normal' | 'spacious';
  };
  founderStory?: {
    enabled: boolean; title: string; body: string;
    credentials?: string; ctaHook?: string;
  };
  leadPopup?: {
    enabled: boolean; title: string; body: string;
    ctaText: string; imageUrl?: string; delaySeconds: number; // 0-120, default 8
  };
  pages: Page[];        // multi-page source of truth (FIT-209)
  sections?: Section[]; // @deprecated legacy single-page list, mirrored to the home page
};

Back-compat shim

• pages[] is the source of truth. Legacy rows carry only sections (no pages).
• getMinisitePages(content) (in @taikan/shared, mirrored client-side by getPages in apps/minisites/src/lib/pages.ts) returns content.pages when present, otherwise wraps content.sections into a single home page.
• The API service ensurePages() upgrades rows in place: shims legacy sections into Home, backfills missing default pages (disabled), and backfills missing section types into Home. It keeps content.sections mirrored to the Home page’s sections.

New section data shapes

• social (SocialSectionData): { title, description, instagramHandle?, instagramUrl?, tiktokUrl?, facebookUrl?, youtubeUrl?, posts: { imageUrl, link? }[] }. Manual.
• events (EventsSectionData): { title, description, showEventIds: string[] }. Config-only; the renderer pulls rows from platformData.events[] (empty showEventIds shows all upcoming published events).

pricing section data (PricingSectionData)

{ title, featuredPlanIds: string[], highlightPlanId?, valuePillar?, stackReductionNote?, ctaMode: 'lead' | 'purchase' }.

ctaMode (FIT-287, default 'lead') is the owner’s opt-in toggle for the purchase CTA — set via the PricingEditor’s radio control, published like any other section field. On its own it changes nothing: the Astro renderer never reads ctaMode directly, only the API-computed platformData.joinUrl, which additionally requires the minisite-plan-purchase flag and an active payment config (see Pricing DTO extensions above). No migration — the field lives in the existing content/published_content jsonb and defaults old rows to 'lead' on parse.

The Astro page treats data as opaque per-section JSON; schema is enforced in the dashboard editor and @taikan/shared.