> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email

> Build emails from approved components and templates, then send each one personalized for every recipient.

Set up how your emails look once, and every email after that is faster and more consistent. allGood builds email in three layers. Each layer answers a different question, and a different person usually owns it.

| Layer | Answers | What varies there |
| - | - | - |
| **Email component** | What does this piece look like, and what is safe to change on it? | Nothing. A component is the approved, reusable piece itself, such as a hero, a button, or a footer. |
| **Email template** | How is this kind of email put together, and what does it need from the writer? | The design is fixed: this header, this footer, this button, arranged from components. The copy changes, and you declare it once as a **copy schema**, which is the list of words each email needs to supply, such as headline, offer, and call to action. |
| **Email** | What does this recipient see? | Personalization for each recipient, such as a first name or company, on top of the template's copy. |

Marketing ops usually sets up the first two layers once. A field marketer then makes individual emails by filling in decisions that were already made.

## Start here

> [card] [Components](https://docs.allgoodhq.com/mk/content/email/components/index.md)
>
> The approved blocks every email is built from, and the check that keeps them on-brand.

> [card] [Email templates](https://docs.allgoodhq.com/mk/content/email/templates/index.md)
>
> Reusable designs that list the copy each email needs, so the next email is filled in.

> [card] [Emails](https://docs.allgoodhq.com/mk/content/email/emails/index.md)
>
> Write, preview, test, and send an email, personalized for each recipient.

You don't need all three layers to send. You can write an email on day one with an empty library, and it will send. The layers pay off from the second email onward.

## Set up and send your first email

> [card] [What an email is](https://docs.allgoodhq.com/mk/content/email/emails/what-an-email-is.md)
>
> Learn the layers, starting with the finished message.

> [card] [What an email template is](https://docs.allgoodhq.com/mk/content/email/templates/what-an-email-template-is.md)
>
> Build a template once, then fill it in for every send.

> [card] [Creating an email](https://docs.allgoodhq.com/mk/content/email/emails/creating-an-email.md)
>
> Write your first email from a template and a brief.

> [card] [Before an email can send](https://docs.allgoodhq.com/mk/content/email/emails/before-an-email-can-send.md)
>
> The account setup and content that must be in place to send.

## Related areas

> [card] [Brand guidelines](https://docs.allgoodhq.com/mk/content/brand-guidelines.md)
>
> The colors, fonts, and tone every generator reads.

> [card] [Copy and variants](https://docs.allgoodhq.com/mk/content/copy-and-variants.md)
>
> Why an email's words are their own asset, and how one send delivers more than one version.

> [card] [Publishing and versions](https://docs.allgoodhq.com/mk/content/approvals.md)
>
> How an email goes live and what gets locked in when it does.

> [card] [Email settings](https://docs.allgoodhq.com/mk/settings/email/domains-setup.md)
>
> Your sending domain and authentication.

## Reference

> [card] [Email FAQ](https://docs.allgoodhq.com/mk/content/email/faq.md)
>
> Short answers to common questions.

> [card] [Coming from Marketo or HubSpot](https://docs.allgoodhq.com/mk/content/email/coming-from-marketo-hubspot.md)
>
> How templates, content, and personalization carry over.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.