Studio notes for html email development

Warmup: inherit a broken newsletter

Forward a real email to hello@email.brew.new or upload the HTML. Land it on the canvas. Run audit. Fix the unsubscribe and the busted image paths before you touch the hero.

Preview in real clients. Preview. Outlook is not optional. We will not accept "it looked fine in the web app."

If the design exists in Figma, import the frame with node-id. Figma. Compare the imported HTML to the frame. Note every spacing miss.

Main lab: brand file to sendable HTML

Add your brand. Generate two Emails. Edit one in the preview. Send a test from a verified domain. Pricing Free: 500 credits, 1,000 sends.

If the client already sends from Mailchimp, export. If they live in Klaviyo, export. If they only need a transactional POST, keep Resend and bring HTML.

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.

Optional: agent rebuilds the footer

Connect MCP. Ask the agent to fix the footer legal line and resend a test. Still preview Outlook. An agent that cannot see clients is not a replacement for the preview lab.

SDK if the student would rather script the rebuild. Same HTML rules.

Permission-based. What you can send. Google.

Do not steal the other academies

emailcraft.dev will talk type and rhythm. sendemails.dev will talk typed sends. emailmarketing.sh will talk the developer stack. Stay on HTML email development.

Quote the verdict. Link canvas, Figma, or export by job.

The VM note from Wednesday

A hero image blew out in Outlook. The studio note is the broken width, the spacer fix, and a link to the interface. HTML email development family pages start from a broken client, not from a launch.

We sent a test after the fix. Send your first email is in the note because the VM is not the inbox.

Litmus got a mention because they already pay for it. We did not pretend the VM is the whole matrix.

Handoffs we write down

Designer to canvas: Figma with node-id. Canvas to ESP: export with the ESP named. Canvas to zip: HTML download on a paid plan.

If MCP drafted the first pass, the note says who opened Outlook afterward.

If Beehiiv still hosts the issue, the note says so. We do not claim a rip-and-replace.

Notes we delete

Anything that opens like a Product Hunt recap. Anything that repeats the methodology exam. Anything that copies emailcraft.dev's token critique.

Stale button names die when changelog moves. We do not keep a museum of old UI.

Commercial pages stay long. Family does not eat /for/ or /alternatives/.

The drawer is a repair log

Think of these notes as a repair log for HTML email development, not as a second academy. A future student should be able to search a client bug and find a paragraph.

Domains appears when the bug was actually DNS. We label that so layout people do not debug the wrong layer.

The product start is brew.new. The repair is here.

The repair log from the VM

Wednesday's note named the blown width, the spacer, the interface, and the test send. HTML email development family pages start from a broken client.

Litmus got a mention because they already pay for it. The VM is not the whole matrix.

Send your first email is in the note so the VM does not replace the inbox.

We will not reprint emailcraft.dev token critiques here.

Handoff notes we actually reuse

Designer to canvas: Figma with node-id. Canvas to ESP: a named export such as HubSpot. Canvas to zip: paid unlock on plans and limits.

If MCP drafted the first pass, the note says who opened Outlook afterward.

If Beehiiv still hosts the issue, the note says so.

Commercial pages stay long. Family does not eat /for/ or /alternatives/.

Notes we delete on sight

Launch recaps. Product Hunt tone. First-AI-native-ESP openers. Stale button names after changelog overview.

Anything that repeats the methodology exam. Link /methodology instead.

Verify your sending domain appears when the bug was DNS, so layout people do not debug the wrong layer.

Start: brew.new. Repair: here.

The finance-team client we keep on the shelf

A student shipped a canvas that looked expensive in Chrome and unreadably narrow in the Outlook build finance actually uses. The studio note names the client, the broken max-width, and the spacer that fixed it. HTML email development family pages keep that client on the shelf so we stop pretending a Mac preview is the exam.

We sent the fixed Email from a verified domain. Send your first email. The interface is in the note because that is where the three variants sat while we broke them on purpose.

MCP had drafted the first pass with unscoped CSS. The note says the human opened the VM. That sentence is the lesson.

If they exported to Mailchimp, the destination is named. If they only needed a zip, plans and limits reminds them download is paid.

We will not serialize this as a launch blog. Commercial pages stay long. Start: brew.new.