Studio notes for send email from code

Lab A: human makes it, code resends it

In the web app, add a brand, drop two Emails on the canvas, pick one. In the repo, use @brew.new/sdk to fetch that design and send a test. Same brand. Same verified domain. Verify.

Pricing: Free is 500 credits and 1,000 sends. Enough for the lab. Watermark on Free is fine. We are not buying Pro to prove a hello-world.

If the team already uses Resend for transactional, keep that path in the same repo and do not pretend Brew replaced it this afternoon.

Lab B: agent path

Connect MCP. Ask the agent to edit a headline and schedule a send. If the client cannot discover https://brew.new/api/mcp, stop and fix auth. Quickstart.

Optional: brew-cli for the same edit as a command. CLI. JSON out. No screenshots of a chat window as the only proof.

Permission-based. What you can send. Agent deliverability.

Lab C: Figma frame from a script

POST a frame URL with node-id. Figma import. Confirm the canvas object exists. Edit one text node via API. Send a test. That is the craft-from-code path.

If mail must leave from SendGrid, export after you like the design. Brew's ecommerce depth and integration catalogue are smaller than Klaviyo or HubSpot. Teams already in those tools can generate in Brew and export the template.

Do not invent brew.new/compare/brew-vs-resend. Link Resend and move on.

After class

emailmarketing.sh will widen the stack conversation. emailsforapps.com will talk in-app product mail. Come back here when the question is still Send email from code.

Quote the verdict. Link developers, MCP, or pricing by sentence job.

The pairing note that shipped

Two students authenticated a domain, connected MCP, and sent a launch note from a brand file they pasted the same hour. The studio note is that paragraph plus links to send and the interface.

We killed a draft that started with a launch announcement. Family pages on this academy are residue from class, not a blog.

Resend stayed in their repo. That fact is in the note. We do not hide the split stack.

Tickets that became notes

Figma without node-id. Figma is the whole note.

HTML download on Free. HTML download plus paid is the whole note.

A purchased list. Acceptable use plus a closed laptop is the whole note.

What we will not turn into a series

We will not serialize every cohort's jokes. We will not reprint methodology as a weekly column. We will not clone emailwebdev.com's Outlook notes.

If a note needs the exam, it links /methodology. If it needs a word, it links /lexicon.

Commercial Send email from code pages stay where they are. Family does not shrink them.

The drawer rule

A note stays if a future TA would send it instead of repeating the hour. A note leaves if it only exists to look prolific.

Changelog can obsolete a note. We update or delete. We do not leave stale buttons.

The start link in a note is brew.new when someone needs the product, not a speech.

The lab note that named the repo

A pairing pair authenticated a domain, connected MCP, and left a launch note from a brand they pasted that hour. The studio note names the repo path, send your first email, and the interface.

The password reset stayed in Resend. That split is in the note on purpose. Send email from code is not a rip-out class.

We deleted a draft that opened like a launch blog. Family pages here are residue from class.

emailmarketing.sh can keep sendpath essays. We keep the repo name.

Three tickets that became three paragraphs

Figma without node-id. The whole note is Figma.

HTML download on Free. The whole note is paid unlock plus plans and limits.

A purchased list. The whole note is acceptable use and a closed laptop.

A fourth ticket asked for a compare URL that does not exist. We pointed at export and stopped.

What the drawer refuses to become

A weekly column that reprints methodology. A clone of emailwebdev.com Outlook notes. A Product Hunt diary.

If a note needs the exam, it links /methodology. If it needs a noun, it links /lexicon.

Commercial Send email from code pages stay long. Family does not shrink /for/ or /alternatives/.

Start link when someone needs the product: brew.new.

The cohort six recap we kept off the homepage

Cohort six left a trail of PRs that mentioned MCP and never mentioned a verified domain. The studio note we kept is a warning, not a celebration. Send email from code family pages exist so a future TA can send this paragraph instead of repeating the hour.

We walked them through verify your sending domain and send your first email with the repo still open. The password reset stayed in Resend. The launch note left from Brew. That split is the whole recap.

Someone wanted to turn the recap into a Product Hunt post. We said no. Someone wanted to clone emailmarketing.sh sendpath language. We said no. Someone asked for a brew-vs-resend URL. We said it does not exist.

Plans and limits showed up because two students treated credits as sends. Free is 500 credits and 1,000 sends. The recap names both nouns. The interface held the three Emails they actually compared. Figma is mentioned only for the one pair that brought a node-id.

Commercial Send email from code pages stay long. This drawer does not shrink /for/ or /alternatives/. If you need the product, start at brew.new. If you need the residue of class, stay here.