💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

원문 렌더가 준비되기 전까지 텍스트 가이드로 표시합니다.

Prologue — 1998's `table` is still alive

If you have only written modern HTML, the first time you open an email template the shock never quite leaves you. CSS Grid is unsafe. Flexbox is unsafe. Even `div`-based layouts are unsafe. Anyone who has ever met Outlook (specifically the Microsoft 365 desktop client with Word's rendering engine) knows the truth: the 1998-vintage `table` layout is still effectively the only universally compatible technique.

And yet, on top of that fossil, the period from 2024 to 2026 has been surprisingly lively. Resend's react-email has become the de-facto standard for indie startups. Maizzle has carried Tailwind CSS into email-land. MJML has kept its position as the open component standard. Postmark's server-side templates blur the line between marketing and engineering with a single Mustache expression. At the same time, drag-and-drop SaaS — Stripo, BEE, Stensul, Unlayer — keeps absorbing more of the marketing department's workload.

This article walks all four buckets — **code (Maizzle, Cerberus)**, **component DSL (MJML, react-email, Foundation for Emails, HEML)**, **server-side templates (Postmark, HubSpot)**, **drag-and-drop SaaS (Stripo, BEE, Stensul, Unlayer, mosaico, Email-Builder.js, Tabular)** — and also covers dark mode, accessibility, MIME multipart, AMP for Email, and what Korean and Japanese teams actually do.

1. The 2026 HTML email map — code / component / drag-and-drop / SaaS

The space breaks into roughly four buckets.

| --- | --- | --- | --- |

The boundaries blur. Maizzle is code-first but works as a component library too. react-email is a component DSL but is still code-first in spirit. Stripo is drag-and-drop but lets you edit raw HTML. Treat the table as a starting point, not a taxonomy.

Five meaningful trends as of May 2026:

1. **react-email (Resend) dominance** — informal estimates put indie / startup adoption above 80 percent.

2. **Maizzle's quiet rise** — Tailwind shops adopt it without thinking twice.

3. **MJML's stability era** — fewer big features, more focus on integrations and AI assistance.

4. **Drag-and-drop SaaS absorbing marketing** — Stripo / BEE / Stensul each find a niche.

5. **The de-facto death of AMP for Email** — six years after launch, nearly every adopter has rolled back.

2. Why email is still hard — client fragmentation

The 2026 client share, roughly:

- **Apple Mail (iOS / macOS)** — about 55 percent. The best CSS support; automatic dark-mode inversion.

- **Gmail (web / app)** — about 28 percent. Accepts the `<style>` tag (since 2016), but `clip-path` and `mix-blend-mode` are unreliable.

- **Outlook (Microsoft 365 desktop, Outlook.com, Outlook mobile)** — about 10 percent. **The root of all suffering.** The desktop client uses Word's rendering engine (MSO), while web / mobile / Mac use separate engines, so the same message can render three different ways.

- **Everything else (Yahoo, AOL, Samsung Mail, Japanese K-9, Korean Daum Mail, etc.)** — about 7 percent combined.

The problem is Outlook desktop. Microsoft pushed "New Outlook" in 2024, but in 2026 about 60 percent of corporate environments still run the Word engine. The Word engine:

- Does not support CSS Grid or Flexbox.

- Does not render `background-image` (you fall back to VML).

- Ignores certain `margin` declarations.

- Does not honor `border-radius`.

- Falls back to Times New Roman if your font stack is too modern.

So in 2026 the email template still leans on `table` + `td` + `align="center"`, exactly as it did in 1998. Maizzle, MJML, and react-email all compile down to that.

Body goes here

The critical piece is `role="presentation"` — it tells screen readers the table is layout, not data. Accessibility is covered in chapter 13.

3. Maizzle — the TailwindCSS-driven workflow

3.1 Origin

Maizzle started in 2018 from Romanian developer Cosmin Popovici. The core idea: **use Tailwind for email**. Tailwind is a utility-class framework built for web pages, but Maizzle adapts the same developer experience to email. Maizzle 5, released in 2024, was rewritten on top of Vite, and the current line is 6.x.

npx create-maizzle

Maizzle Starter? Default

Project name? my-emails

cd my-emails

npm install

npm run dev

Default layout:

my-emails/

src/

components/ # reusable components

layouts/ # layouts (main.html etc.)

templates/ # actual emails (welcome.html etc.)

tailwind.config.js

config.js

package.json

3.2 How it works

At build time Maizzle:

1. Converts Tailwind classes into inline styles.

2. Inlines the classes that cannot survive in a `<style>` block.

3. Leaves media queries in `<style>` (Outlook can ignore them, that's fine).

4. Minifies the HTML.

5. Optionally generates a plain-text version.

You write this:

You ship this:

3.3 Strengths

- **Tailwind, exactly as on the web.** Web teams need to learn nothing new.

- **`x-component`** for reusable headers / footers.

- **Environment builds** — different data injected for dev / staging / production.

- **MJML interop** — you can route through MJML if you need to.

- **Plain-text auto-generation** through `juice`.

3.4 Weaknesses

- **Tailwind has a learning curve** if your team has never used it.

- **Not appropriate for marketing teams** that need drag-and-drop.

- **Simpler component model than React.** No JSX-style expressiveness.

Maizzle shines when the frontend team owns the email pipeline directly.

4. MJML — Mailjet's component DSL

4.1 History

Mailjet (now Sinch Email) open-sourced MJML in 2015. It is pronounced "M-J-M-L". The project is an email-specific markup language plus a compiler that produces 1998-compatible HTML.

Get started

4.2 What is good

- Semantic components: `mj-section`, `mj-column`, `mj-button`, `mj-image`, `mj-divider`.

- **Responsive by default** — `mj-column` stacks on mobile automatically.

- **VS Code extension** with live preview.

- **CLI** — `mjml input.mjml -o output.html`.

- **Node library** — `mjml2html()` for server-side rendering.

const { html, errors } = mjml2html(mjmlSource, {

minify: true,

keepComments: false,

})

4.3 Weaknesses

- **You have to learn MJML.** A barrier for designers.

- **Variable substitution is bring-your-own** — you bolt Handlebars / Mustache / Liquid on top.

- **i18n is not provided** — you write your own layer.

- **AI tooling is thinner than react-email** — MJML AI exists but the broader React ecosystem moves faster.

MJML is still the right answer for teams that want an open standard but do not want a React dependency.

5. react-email (Resend) — the JSX-native option

5.1 How it took off

Resend founder Zeno Rocha published react-email in 2023. The premise was simple: "I want to write email as components, in JSX." Riding Resend's growth, it became the de-facto choice in the indie / startup world by 2024, and 4.x landed in January 2026.

npm install react-email @react-email/components -D

npx react-email dev # local preview server

// emails/welcome.jsx

Body,

Button,

Container,

Head,

Heading,

Html,

Preview,

Section,

Text,

} from '@react-email/components'

export default function Welcome({ name = 'friend' }) {

return (

Get started

)

}

const main = { backgroundColor: '#f8fafc', fontFamily: 'Inter, Arial, sans-serif' }

const container = { maxWidth: 600, margin: '0 auto', backgroundColor: '#fff', padding: 24 }

const h1 = { fontSize: 24, fontWeight: 700, color: '#1e293b' }

const btn = { backgroundColor: '#3b82f6', color: '#fff', padding: '12px 24px', borderRadius: 6 }

(JSX curly braces above are inside a code block, so they are inert. Never expose bare curly identifiers in prose.)

5.2 Strengths

- **Zero learning curve for React teams.**

- **The `@react-email/components` library** ships `Button`, `Container`, `Section`, `Heading`, `Img`, `Hr`, `Link`, and more.

- **The local preview server (`npx react-email dev`)** is the best DX in the space.

- **HTML and plain-text in one call** — `render(<Welcome />)`, `render(<Welcome />, { plainText: true })`.

- **First-class Resend integration** — pass `react` to the Resend SDK and the rendering happens for you.

const resend = new Resend(process.env.RESEND_API_KEY)

await resend.emails.send({

from: 'Acme <hello@mail.acme.com>',

to: ['user@example.com'],

subject: 'Welcome',

react: <Welcome name="Youngju" />,

})

5.3 Weaknesses

- **React dependency.** Less obvious for PHP / Ruby / Go teams (an SSR microservice helps, but adds complexity).

- **Outlook Word-engine compatibility is still your problem** — clean components can still break on busy layouts.

- **Dark-mode tokens are DIY** — there is no Tailwind-style design-token system out of the box.

5.4 react-email vs MJML

Same conceptual model, different ergonomics:

- **MJML**: custom DSL into HTML. React-agnostic.

- **react-email**: JSX into HTML. Composable, testable, and Storybook-friendly.

If you are a React team, react-email. Otherwise, MJML.

6. Postmark Templates — server-side variable substitution

6.1 Positioning

Postmark is a transactional-first ESP with a strong template system based on MJML plus Mustachio (a Mustache variant). Postmark was acquired by ActiveCampaign in 2024 and continues to run as a standalone product in 2026.

You write the template with Mustachio placeholders, then inject data at send time through the API.

const client = new ServerClient(process.env.POSTMARK_TOKEN)

await client.sendEmailWithTemplate({

From: 'orders@example.com',

To: 'user@example.com',

TemplateAlias: 'order-confirmation',

TemplateModel: {

name: 'Youngju',

order_id: 'A-1234',

items: [

{ name: 'Book', quantity: 1, total_usd: '20.00' },

{ name: 'Coffee', quantity: 2, total_usd: '12.00' },

tracking_url: 'https://example.com/track/A-1234',

})

6.2 Strengths

- **Marketing can edit copy directly** without touching send code.

- **Clean i18n** — KO / EN / JA variants of the same template tracked as aliases.

- **MJML-based editor** with side-by-side visual and code editing.

- **A/B tests and versioning** built into the product.

6.3 Weaknesses

- **Postmark lock-in** — switching ESPs means porting every template.

- **Disconnected from your code workflow** — template edits do not show up in your Git history.

- **Weaker logic** — fewer expressive primitives than Liquid.

Server-side templates work best when "marketing edits copy frequently, structure rarely" holds true.

6.4 Compared to SendGrid Dynamic Templates / HubSpot

- **SendGrid Dynamic Templates** — Handlebars-based, similar to Postmark, weaker editor UX.

- **HubSpot templates** — use HubL, deeply integrated with HubSpot's marketing automation, overkill for transactional mail.

7. Foundation for Emails (ZURB) — the classic framework

7.1 ZURB's legacy

ZURB was famous in the early 2010s for the Foundation CSS framework (Bootstrap's main rival). In 2015 they spun off an email-specific branch named Foundation for Emails (codename Ink). Version 2 shipped in 2017 and there have been no large updates since, but the project is still maintained.

With the Inky markup you write `container`, `row`, `columns`, `button`, and the compiler converts them to `table`-based HTML. MJML's spiritual ancestor.

7.2 Is it worth using in 2026?

For new projects, mostly no. MJML and react-email are better in nearly every dimension. But:

- Teams with existing **ZURB / Foundation assets**.

- **Ruby on Rails** shops, where the `foundation_emails-sass` gem is well-supported.

- Anyone who finds the **`mj-` prefix** of MJML aesthetically painful.

For those, it remains reasonable.

8. Cerberus templates (Ted Goas)

8.1 What it is

Cerberus is a collection of **plain HTML email templates** published around 2013 by designer and developer Ted Goas. No build tooling — you copy the HTML file and edit. The repository is still maintained in 2026 with around 8.5k GitHub stars.

Three core templates:

1. **`cerberus-fluid.html`** — single column, mobile-first.

2. **`cerberus-responsive.html`** — media-query-based responsive.

3. **`cerberus-hybrid.html`** — Outlook conditional comments plus mobile media queries.

<!--[if (gte mso 9)|(IE)]>

<![endif]-->

style="max-width: 600px; margin: auto;" class="email-container">

<!--[if (gte mso 9)|(IE)]>

<![endif]-->

That is the famous **Outlook conditional comment** pattern. Only Outlook reads the markup inside `<!--[if (gte mso 9)|(IE)]>`. Because Outlook ignores `max-width`, you need a fixed-width 600-pixel `table` for it alone.

8.2 Why it still matters

- **No build tooling** — copy a file, ship.

- **Battle-tested** patterns with more than a decade of production.

- **The best teaching artifact** — Cerberus is the clearest demonstration of why those `table` structures exist.

The fastest learning path for an engineer new to email is: read Cerberus once, then move to Maizzle / MJML / react-email.

9. HEML / mosaico — the other OSS options

9.1 HEML

SparkPost (now MessageBird) open-sourced HEML in 2018.

Concept-wise nearly identical to MJML, but there has been very little movement since 2020. In 2026 it is effectively in **maintenance mode**.

9.2 mosaico

An open-source drag-and-drop editor originally backed by Vox Media. You self-host it and hand it to your marketing team.

- Pros: free, self-hosted.

- Cons: 2010s-era UI, small template library.

Occasionally adopted by teams that want an internal builder but cannot stomach SaaS pricing.

10. Stripo / BEE / Stensul / Unlayer — drag-and-drop SaaS

10.1 Where each tool sits

| --- | --- | --- | --- |

10.2 Stripo

The most friendly general-purpose editor. Supports self-hosting, downloads, and direct ESP send. Strong module library (Shutterstock integration and similar).

10.3 BEE

Originally part of MailUp's BEE Free editor. Its biggest differentiator is the **embedded SDK** — you can drop BEE inside your own SaaS. HubSpot, ClickFunnels, and many others OEM it.

10.4 Stensul

Enterprise-only. Not really an editor so much as an **email collaboration workflow** — brand-guideline enforcement, approval routing, multi-language translation pipelines. Large finance / pharma / telco shops are the primary customers.

10.5 Unlayer

Built for SaaS embedding. The **react-email-editor** package drops Unlayer into your React product in under five minutes.

export default function Editor() {

return (

projectId={12345}

onLoad={(unlayer) => {

// ready

}}

onReady={(unlayer) => {

unlayer.exportHtml((data) => {

console.log(data.html)

})

}}

)

}

(Again, the JSX braces are inside a code block.)

10.6 mosaico vs SaaS — the trade-off

- **SaaS** — instant, great template library, but a monthly bill and data sitting elsewhere.

- **Self-hosted mosaico** — free, data stays inside, but operational cost and dated UI.

11. Email-Builder.js (Microsoft) / Tabular — the newcomers

11.1 Email-Builder.js

Open-sourced by Microsoft in 2024. React-based email builder. The interesting bit is **the company behind Outlook is shipping the tool**.

const document = {

root: {

type: 'EmailLayout',

data: {

backdropColor: '#F5F5F5',

canvasColor: '#FFFFFF',

children: ['block-1', 'block-2'],

'block-1': {

type: 'Heading',

data: { props: { text: 'Welcome', level: 'h1' } },

'block-2': {

type: 'Text',

data: { props: { text: 'Thanks for signing up.' } },

}

export default function Preview() {

return <Reader document={document} rootBlockId="root" />

}

- Pros: Microsoft's commitment to Outlook compatibility.

- Cons: smaller ecosystem than react-email so far.

11.2 Tabular

A 2024 drag-and-drop SaaS newcomer. Differentiator: **AI-first**. It generates copy, imagery, and layout from LLMs as a primary workflow. Already gaining traction with indie marketing teams.

12. Litmus / Email on Acid — testing

12.1 Origins

There are well over a hundred email clients and you cannot know how your email renders without actually opening it in each one. Litmus and Email on Acid exist because of that.

- **Litmus** — founded 2005 in the UK. Acquired by Cision in 2022.

- **Email on Acid** — founded 2010 in Colorado. Acquired by AWeber parent Volaris Group in 2022.

Both products are functionally similar:

1. **Client previews** — screenshots across 90 to 100+ clients.

2. **Spam analysis** — how SpamAssassin, Microsoft, and others score the message.

3. **Link / image checks** — broken links, missing images.

4. **Accessibility checks** — alt text, color contrast, font size.

5. **Analytics** — opens and clicks.

12.2 The workflow

The typical loop:

1. Build HTML with Maizzle / MJML / react-email.

2. Upload to Litmus or Email on Acid (directly or via your ESP integration).

3. Review per-client previews.

4. Fix the broken ones and re-upload.

5. When it passes, send through the ESP.

// Hypothetical Litmus preview request

const res = await fetch('https://api.litmus.com/v1/emails', {

method: 'POST',

headers: {

Authorization: 'Bearer ' + process.env.LITMUS_TOKEN,

'Content-Type': 'application/json',

body: JSON.stringify({

html: htmlSource,

subject: 'Test',

clients: ['outlook2021', 'gmail-web', 'ios-mail-17', 'samsung-mail'],

}),

})

12.3 Pricing

Both are expensive in 2026. Entry pricing sits around `$99/month`; serious usage lands at `$199 to $400/month`. Indie developers usually start with **Mailtrap**, **HTML Email Check**, or **PutsMail** (Litmus's free tool).

13. Dark mode, accessibility, MIME multipart, AMP for Email

13.1 Dark mode — Outlook's new hell

By 2024 every major client supports dark mode, but they implement it three different ways.

1. **Apple Mail (iOS / macOS)** — honors `prefers-color-scheme: dark` honestly. The clean case.

2. **Outlook desktop / mobile** — **inverts colors itself**. White backgrounds become black, but only some colors invert, so logos break.

3. **Gmail** — partial inversion. The result depends on the combination of client and OS settings.

A typical defense:

/* Color-scheme metadata */

:root {

color-scheme: light dark;

supported-color-schemes: light dark;

}

@media (prefers-color-scheme: dark) {

.body-bg { background-color: #0f172a !important; }

.text { color: #e2e8f0 !important; }

}

/* Try to stop Outlook from forcing inversion (client-dependent) */

[data-ogsc] .body-bg { background-color: #0f172a !important; }

[data-ogsc] .text { color: #e2e8f0 !important; }

The core rule: **logos and icons should be SVG, or ship both dark and light versions** — so inversion does not destroy your brand.

13.2 Accessibility — WCAG, for email

Email is subject to WCAG 2.2 AA. The short checklist:

- Add `role="presentation"` to every layout `table`.

- Image `alt` attributes are mandatory. Decorative? Use `alt=""`.

- Body text contrast at least 4.5:1 — `#666` on `#fff` fails.

- Body font no smaller than 14px, ideally 16px.

- Links should be distinguishable by more than color — add underlines.

- Set `lang` on the root — `<html lang="en">` or `<html lang="ja">`.

- `prefers-reduced-motion` — GIFs without pause controls should be avoided.

13.3 MIME multipart — plain text is non-optional

Virtually every marketing email should go out as `multipart/alternative`. Two reasons.

1. **A missing plain-text part raises spam scores** — SpamAssassin and friends treat HTML-only as suspicious.

2. **Apple Watch, text-only clients, and screen readers** consume the plain-text part.

MIME-Version: 1.0

Content-Type: multipart/alternative; boundary="boundary42"

--boundary42

Content-Type: text/plain; charset=utf-8

Welcome.

Thanks for signing up. Open this link to get started:

https://example.com/start

--boundary42

Content-Type: text/html; charset=utf-8

--boundary42--

react-email generates this with `render(<Welcome />, { plainText: true })`. Maizzle does it through `juice` automatically.

13.4 AMP for Email — almost dead, not quite

Google launched AMP for Email in 2019 to bring **dynamic content into the inbox** — form submission, carousels, live-updating data.

<!DOCTYPE html>

.container { padding: 16px; }

In 2026 it is effectively dead. Why:

- **Only Gmail, Yahoo, and Mail.ru support it.** Outlook and Apple Mail do not.

- **Sender registration is cumbersome** — you have to enroll with Google directly.

- **Maintenance cost beats the payoff** — you still need the HTML fallback.

Booking.com, Pinterest, and other early adopters mostly rolled back around 2024. If you are starting now, **ignore AMP**.

14. AI in email — MJML AI, Maizzle AI?, ChatGPT for design

14.1 MJML AI

Mailjet's 2024 tool. You describe the email in natural language — "welcome email, blue tones, one CTA button" — and it returns MJML.

[Input]

Make a sign-up welcome email. Blue tones, company logo on top, greeting, CTA button "Get started", social links at the bottom.

[Output]

...

Quality is above average. The design usually needs a human pass to feel less generic.

14.2 Maizzle / react-email + ChatGPT

No dedicated tool required. Asking ChatGPT or Claude to "write a Maizzle component for X" works well in 2026 — LLMs understand email markup well enough.

Effective prompt hints:

- **Call out Outlook compatibility** — "must render in Outlook desktop with the Word engine".

- **Insist on `table`-based layouts** — "no Flexbox; use `table` layouts".

- **Specify responsive behavior** — "single column below 480px".

- **Specify dark mode** — "include `prefers-color-scheme: dark` media queries".

14.3 Tabular's AI integration

Tabular treats LLM-driven body generation as a first-class workflow. The marketing team sets a brand voice and Tabular drafts the weekly newsletter. Indie marketing teams are picking it up fast in 2026.

15. Korea / Japan — Toss, Kakao, Mercari, Cookpad

15.1 Korea

- **Toss email** — Transactional and marketing email for Toss runs on internal infrastructure (likely SES-based). Designs are consistent with the Toss design system and look component-driven in a react-email style. Plain-text is always bundled.

- **Kakao email marketing** — Kakao's primary channel is KakaoTalk Biz Message, so email volume is small. KakaoEnterprise and KakaoWorks (B2B) still rely on email and run their own template system.

- **Naver mail on the receiving side** — Naver has dominant share in Korea. If SPF / DKIM / DMARC are misaligned, it sends mail to spam without ceremony. There is also a strong penalty against HTML-only mail. Plain-text is mandatory.

15.2 Japan

- **Mercari email** — Mercari has roughly 100 million members, so email volume is enormous. Past conference talks suggest SendGrid is their primary platform. Templates appear to live on top of their internal design system, with MJML-like components.

- **Cookpad** — recipe service. Daily recommended-recipe emails are a core channel, with strong i18n (JA / EN / ES / AR) infrastructure.

- **Japanese carrier mail** — `docomo.ne.jp`, `softbank.ne.jp`, `ezweb.ne.jp` accounts remain in use. As leftovers from the i-Mode era, they have awkward HTML support and strict limits on image and body size. A peculiarity unique to Japan.

15.3 Korea / Japan in common — review and send timing

- **Conservative review** — marketing copy goes through legal and compliance review more often than in the U.S. That favors Postmark and Stensul, which support collaborative workflows.

- **Send timing** — open rates peak between 9am and 10am on weekdays in both Korea and Japan (2025 SendGrid report).

16. Tool selection guide — as of May 2026

By situation:

- **Indie startup / Next.js / Resend stack** — react-email + Resend. No debate.

- **Tailwind shop / Vue / vanilla JS** — Maizzle.

- **PHP / Ruby / Go backend** — MJML CLI plus your own variable substitution.

- **Marketing team edits copy directly** — Postmark Templates, or Stripo / BEE.

- **Enterprise with governance needs** — Stensul, or Salesforce Marketing Cloud Email Studio.

- **Embedding into your own SaaS** — Unlayer (react-email-editor) or BEE SDK.

- **Experimenting with AI-driven workflows** — Tabular.

- **Outlook compatibility is the top priority** — Email-Builder.js from Microsoft.

Whatever the path, **test with Litmus or Email on Acid**. Indie teams can start with the free PutsMail tool.

Dark mode, accessibility, and MIME multipart are **non-negotiable across the board**. And **AMP for Email is safe to ignore** in 2026.

References

- Maizzle official site — [https://maizzle.com](https://maizzle.com)

- MJML official site — [https://mjml.io](https://mjml.io)

- react-email — [https://react.email](https://react.email)

- Resend — [https://resend.com](https://resend.com)

- Postmark Templates — [https://postmarkapp.com/email-templates](https://postmarkapp.com/email-templates)

- Foundation for Emails — [https://get.foundation/emails.html](https://get.foundation/emails.html)

- Cerberus (Ted Goas) — [https://tedgoas.github.io/Cerberus/](https://tedgoas.github.io/Cerberus/)

- HEML — [https://heml.io](https://heml.io)

- mosaico — [https://mosaico.io](https://mosaico.io)

- Stripo — [https://stripo.email](https://stripo.email)

- BEE — [https://beefree.io](https://beefree.io)

- Stensul — [https://stensul.com](https://stensul.com)

- Unlayer — [https://unlayer.com](https://unlayer.com)

- Email-Builder.js (Microsoft) — [https://github.com/usewaypoint/email-builder-js](https://github.com/usewaypoint/email-builder-js)

- Tabular — [https://tabular.email](https://tabular.email)

- Litmus — [https://litmus.com](https://litmus.com)

- Email on Acid — [https://www.emailonacid.com](https://www.emailonacid.com)

- AMP for Email — [https://amp.dev/about/email](https://amp.dev/about/email)

- Email Geeks Slack — [https://email.geeks.chat](https://email.geeks.chat)

- Really Good Emails (inspiration) — [https://reallygoodemails.com](https://reallygoodemails.com)