Skip to content
App Wizard Academy

Access — inside the guide

The Publisher, multi-site.

Same shape as Silver's Publisher workflow — approved draft to live deploy — but reading which site each draft belongs to instead of assuming there's only one.

Four steps

  1. 01

    Watch the drafts table

    Instead of one folder, the trigger is a Supabase row change: status flips to 'approved'. Works the same whether it's site one or site nine.

  2. 02

    Look up the right repo

    Each draft carries a site_id. The workflow reads site_config to know which GitHub repo and Vercel project this particular draft belongs to.

  3. 03

    Commit and deploy

    Same commit-then-deploy step as Silver, just parameterized instead of hardcoded to one repo.

  4. 04

    Update the pages table

    Once live, the new page gets a row in the pages table — this is what the Inventory Agent (next) keeps in sync going forward.

Same shape, looked up per draft

The GitHub owner/repo and Vercel deploy hook come from site_config on every run — no hardcoded site, works the same at one site or nine.

Download publisher-multi-site.json

Next: keeping track of everything that’s actually live. The Inventory Agent.