feat(email): pre-launch marketing campaign for waitlist#356
Open
h4yfans wants to merge 1 commit into
Open
Conversation
Eleven-email drip series for the 400-person Memry waitlist, sent over eight weeks via Resend. Built with React Email. Voice follows the Capacities prosumer/calm reference: one feature per email, hero plus inline screenshots, no marketing varnish. Standalone package at email/, outside the pnpm workspace so marketing infra ships independently of the desktop app. - Shared components: Layout, Eyebrow, HeroImage, InlineImage, Signoff, Footer, constants, styles - 11 emails: introduction, notes (+E2E), inbox, tasks, journal (+sync), projects+calendar, AI agent, graph, offline, launch-week recap, launch-day with download buttons - scripts/send.ts with three modes: --to (test send), --audience (broadcast create), --export (render to HTML + plaintext) Verified: pnpm typecheck clean, all 11 emails render via send --export to 7.8 to 11 KB HTML each (well under Gmail clip threshold).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
added
dependencies
documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
email/outside the pnpm workspace so marketing infra ships independently of the desktop appCadence
Schedule: 1/week W1–W6, 2/week W7, 3 emails W8 (launch week intensity).
Layout
Verified
pnpm install --ignore-workspace— 240 packages installedpnpm typecheck— 0 errorspnpm send <slug> --export— all 11 emails render to HTML (7.8–11 KB each) + plaintextTest plan
cd email && cp .env.example .envand fill in real Resend credentialspnpm dev— visually QA every email at http://localhost:3000placehold.coURLs with real product screenshots before each weekly sendpnpm send 01-introduction --to <your-email>— verify transactional send workspnpm send 01-introduction --audience— verify broadcast appears in Resend dashboard (no auto-send)components/styles.tsfor brand palette if neededNotes for reviewers
stop-sloprules: no em-dashes, no adverbs, no throat-clearing, active voice, varied rhythm. Worth a read-through.--audiencedefaults to create broadcast only, not send.--send-nowis the explicit blast flag to prevent fat-finger blasts.email/.env.exampleusesyour-resend-api-keyplaceholder (passes the repo secret scanner allowlist).pnpm-workspace.yaml) means root-levelpnpm installskips it. Usepnpm install --ignore-workspaceinsideemail/to set it up.