Skip to content
StackQuay

Bilingual hub · agents → site, email, payment links

Ship a microbusiness with agents.

EN + 繁中 playbooks for Hong Kong. Resend, Stripe HK Payment Links, Vercel, then a newsletter.

Stack

Four pieces. Each has one job.

This hub teaches the path, then keeps live keys off until the founder says otherwise.

01

Resend

Newsletter form only. Env placeholder. No live sends from this scaffold.

02

Stripe HK Payment Links

Placeholder CTA. No live payment link until founder approval.

03

Vercel + newsletter

Host the Next.js site. Grow an email list. Sponsors come after traffic.

Spine

Agents draft. You approve. Then the stack.

A short path for a Hong Kong microbusiness: agents write the drafts, the founder approves, then Resend, Stripe HK Payment Links, Vercel, and a newsletter. Sponsors wait until there is traffic.

  1. Agents
  2. Resend
  3. Stripe HK Payment Links
  4. Vercel
  5. Newsletter

Playbooks

Eleven approved drafts. Production still off.

Stripe, Resend, PDPO consent (not legal advice), three different Vercel pages, and one later-stack n8n outline that only drafts a Broadcast (never the Send path). The scaffold overview stays on the index.

Playbook · Stripe

Stripe HK Payment Links — ship a payable link without a storefront.

Create a Stripe-hosted payment link from the Dashboard, share it, and only go live after you finish KYC / bank / 2FA. The bot never flips live charges for you.

Playbook · Stripe

Update Stripe Payment Links after go-live — shipping, consent, Connect (reuse the same URL).

Change shipping, consent checkboxes, and Connect fee or transfer settings on an existing Payment Link. Keep the same shareable URL. Dashboard edit first. STOP: no live charges, no secret keys in chat.

Playbook · Resend

Resend bilingual newsletter — playbook hub list without fake hype.

Verify your domain and set signup copy for an EN + 繁中 newsletter. Contacts and Segments are a separate playbook. Broadcast Send is another. Bot drafts; you approve before any send.

Playbook · Segments

Resend Segments + Contacts — safe targeting (not signup copy, not Send).

Create and list Resend Contacts and Segments, then hand a verified segment_id to the Broadcast draft. Audiences are deprecated. This page does not write the newsletter or press Send.

Playbook · PDPO

HK PDPO — newsletter consent, unsubscribe, and records. Not legal advice.

Not legal advice. STOP: confirm with counsel if needed before a live send or any public privacy-policy claim. Practical outline for consent, unsubscribe, and records on a StackQuay Resend newsletter.

Playbook · Resend

Draft Resend Broadcasts with agents (API) — founder presses Send.

An agent can create a Resend Broadcast draft (subject, HTML, Segment). You review and press Send. Building the Segment is a different playbook. Default send: false. No send on this page.

Playbook · Resend

Cancel or duplicate Resend Broadcasts (agent ops after human-gate).

After a Broadcast is scheduled, queued, or already sent, an agent may cancel (stop remaining sends or revert a schedule to draft) or duplicate (new draft copy). You still own any future Send. No send in this playbook.

Playbook · Later stack

n8n recipe — Resend Broadcast draft only. Secondary later stack.

Secondary (later stack). Thin outline. Schedule Trigger + Google Sheets + Resend Broadcast Create only. STOP: never auto-send. Not the API human-gate page.

Playbook · Vercel

Vercel deploy for this playbook hub — preview first, production only after founder OK.

Put the playbook hub on Vercel as a preview URL you can click and share internally. Env placeholders only. STOP before buying a domain or promoting to production until founder explicitly says go.

Playbook · Vercel agents

Vercel agent toolchain — plugin, MCP, AI Gateway (not the deploy playbook).

Wire coding agents to Vercel’s plugin, MCP, and optional AI Gateway so they can help ship this hub. A preview URL is a different page: the hosting deploy playbook.

Playbook · Analytics

Vercel Web Analytics + weekly traffic recap — measure, don’t host, don’t wire agents.

Turn on Web Analytics (and optional Speed Insights), then fill a weekly recap from Dashboard numbers only. This is not the preview-deploy page and not the agent plugin / MCP page. No invented visitors. No sponsor outreach.

Local only

Keys stay in env placeholders.

Copy this into `.env.local`. Leave values blank. The form UI still works; nothing is charged or emailed.

.env.local

# .env.local — placeholders onlyRESEND_API_KEY=RESEND_FROM=NEXT_PUBLIC_STRIPE_PAYMENT_LINK= # Analytics is not wired.# NEXT_PUBLIC_ANALYTICS_ID=

Get the next playbook by email.

UI only on this scaffold. Submitting shows a local status — Resend is not connected.

Requires `RESEND_API_KEY` in env before a future agent can enable sends. Today the API always returns a placeholder status.

Stripe HK

Payment link stays off.

Stripe HK Payment Links are part of the stack to teach — not a live checkout on this site.