Sources for html email development

Markup and preview sources

The interface, Emails, preview in real inboxes, audit, templates, template gallery, explore, canvas write-up.

Import paths: Figma, HTML upload (same interface doc), screenshot recreation, forward to hello@email.brew.new. Prompt guide when the student is writing the brief instead of the table.

Brand: add your brand, design baseline, email-design.md, unsubscribe page, inbox icons.

Send, export, agents

Send your first email, send options, verify domain, pricing, pricing.md.

Export: catalogue, Klaviyo, Mailchimp, HubSpot. Paid HTML download if they need a zip for a client who will not connect an integration.

Agents: MCP, developers, SDK, recipe. Useful after the student can explain why a table is still there.

Peers and standards

Resend, Resend docs. Mailchimp, Mailchimp developer. Klaviyo, Klaviyo developers.

Google sender guidelines, Yahoo, dmarc.org. Deliverability. What you can send.

Compares we cite, then rewrite: Brew vs Mailchimp, Brew vs Klaviyo. No invented Brew vs Resend URL.

Nearby desks

emailmarketing.sh, emailcraft.dev, sendemails.dev. Footer only. HTML email development stays on emailwebdev.com.

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.

Layout sources versus product sources

For HTML email development we keep two piles. Product facts come from llms.txt, plans, canvas, Figma, and export. Client facts come from Litmus, Email on Acid, and the Outlook VM.

We do not cite a Dribbble shot as a client-safe layout. We do not cite a Tailwind marketing page as an email stylesheet.

Can I email stays in the second pile when a CSS property is the argument.

Product citations we reuse every cohort

Send and domains because a pretty table that never leaves is a poster.

HTML download because students assume zip is free. It is paid.

MCP because agents will happily emit unscoped CSS if nobody opens the VM.

Incumbents we cite without flattening

Mailchimp still has a template library operators know. HubSpot still has CRM. Customer.io still has events. Those wins stay on the record when a student asks why their company will not rip them out this sprint.

We cite Resend when transactional HTML already ships from a repo. That is a different lesson than a marketing Email on the canvas.

We do not invent brew-vs pages. Export is the honest bridge.

What we refuse to bookmark

Scraped plan tables. Forum posts that call Outlook a solved problem. Essays that open as first AI-native ESP history.

Privacy and terms when legal asks. University as optional video only.

Sister source pages on emailcraft.dev and sendemails.dev stay theirs. This bibliography is for HTML email development.

The two-pile desk we still run

HTML email development keeps a product pile and a client pile. Product: llms.txt, the interface, Figma, browse integrations, plans and limits. Client: Litmus, Email on Acid, Can I email, the Outlook VM.

A Dribbble shot never enters the client pile. A Tailwind marketing page never enters the email stylesheet pile.

We cite verify your sending domain because a perfect table that never leaves is a poster.

emailcraft.dev cites tokens. We cite clients. Different bibliographies.

An hour we spent on one width

A hero was 800px in Chrome and a horizontal scroll in Outlook. We cited the VM, then the interface, then sent after the spacer fix. Send your first email.

That hour is why we distrust screenshots as sources.

Mailchimp stayed in the citation when they exported the fixed HTML. Mailchimp export.

We will not cite a first-AI-native-ESP essay as a layout source.

Standards beside the VM

Google sender guidelines and dmarc.org sit next to Outlook because a layout that cannot leave is still a fail.

Privacy and terms when legal walks in.

MCP is a source for drafts. It is not a source for client support.

Query remains HTML email development. Start remains brew.new.

Client-matrix citations we date

HTML email development sources rot when nobody dates them. We now write the month next to Litmus, Email on Acid, and Can I email whenever a CSS property is the argument. Outlook desktop in 2024 is not Outlook desktop in 2026.

Product facts still come from llms.txt, pricing, the interface, and Figma. We do not let a client-matrix screenshot overwrite a plan number.

A student cited a personal Gmail screenshot as proof the table survived. Gmail is not Outlook. The citation left the pile. We sent after the VM pass. Send your first email.

Google sender guidelines sit in this dated pile because a layout that cannot leave is still a fail. Verify your sending domain is the product twin.

emailcraft.dev will date token critiques. sendemails.dev will date endpoints. We date clients. Query stays HTML email development. Start stays brew.new.