DEPLOY // HOST // SHIP

Deploy Guide

This package works as a static site. Cloudflare Pages supports direct upload or Git-based deployments, GitHub Pages can publish from a branch or Actions, Netlify supports form detection on HTML forms using data-netlify="true", and Supabase browser clients are initialized with a project URL and anon key. citeturn942164search4turn942164search5turn942164search2turn942164search3

Cloudflare Pages

Connect a Git repository or use direct upload. For this package, no build step is required because the site is already static. Cloudflare Pages supports build configuration and direct upload workflows. citeturn942164search0turn942164search16

Build command: leave empty Output directory: /

GitHub Pages

GitHub Pages can publish static HTML, CSS, and JavaScript directly from a repository branch or from a GitHub Actions workflow. Publishing from the repository root is enough for this package. citeturn942164search13turn942164search5

Repo settings → Pages → Source Branch: main Folder: / (root)

Netlify Forms

Netlify detects HTML forms with a data-netlify="true" or netlify attribute when the form is present in the deployed HTML. Static blueprint forms matter for detection. citeturn942164search2turn942164search14

Submit page is already wired. Deploy the site, then submissions appear in Netlify.

Supabase

Supabase browser clients are created with the project URL and anon key. Use the included schema file to create tables for resources, clicks, and submissions. Never expose the service role key in browser code. citeturn942164search3turn942164search19turn942164search15

import { createClient } from '@supabase/supabase-js' const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY)