This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
Environment variables
Set in Vercel (Production and Preview). Used by api/partner-application.ts, the server-side function behind the unlisted Launch Day partner application page (/partners/launch-day/apply/):
| Name | Value | Sensitive |
|---|
LAUNCH_DAY_API_URL | https://launchday-chi.vercel.app (Launch Day base URL) | no |
PARTNER_APPLICATION_SECRET | Shared secret. Must match the same variable in the Launch Day Vercel project; rotating it means changing both projects. | yes |
If either is unset the endpoint returns a friendly 503 and never forwards. RESEND_API_KEY is used only by the legacy app/api/contact route.
Note: vercel.json makes this site deploy as static files (root index.html), so the Next.js app/ directory, including app/api/contact, is not served in production. Serverless endpoints must live in the root api/ directory. The partner page is unlisted by design: do not link it from nav, footer, or home, and do not add it to a sitemap.
Partner application form contract
Page: partners/launch-day/apply/index.html (static). It POSTs JSON (or a native urlencoded form post without JS) to api/partner-application.ts, which forwards server-to-server to ${LAUNCH_DAY_API_URL}/api/partner-application with the x-partner-application-secret header.
Fields (all required except honeypot, which must stay empty):
| Field | Notes |
|---|
shopDomain | Store handle (my-flower-farm) or full .myshopify.com address. The page appends .myshopify.com to a bare handle; Launch Day normalizes again. |
email | Support email (notifications, issues, alerts). |
newsletterEmail | Newsletter email. Applicants type it themselves (no "same as" shortcut, by design). |
consent | Newsletter consent checkbox. |
honeypot | Bot trap, hidden from people. |
The function validates shopDomain length and the shape/length of email and newsletterEmail (400 with field) before forwarding {shopDomain, email, newsletterEmail, consent, honeypot}. Launch Day may return 400/409/429 with {error, field?}; field is passed through when it is one of shopDomain, email, newsletterEmail, consent, and the page shows the error beside that field. A real end-to-end submit needs the Launch Day change that accepts newsletterEmail deployed first.
