> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/getting-started/campaign-basics/basics-creating-email.md).
# Creating your first email
This guide walks you through creating an email in eMarketeer, from setting it up to editing content blocks and adding the final touches.
{% hint style="warning" %}
To create a new email it is required that you create a campaign first. If you don't have a campaign ready, see [How to create a new campaign](/getting-started/campaign-basics/create-new-campaign.md).
{% endhint %}
{% hint style="info" %}
The example builds an event invitation email, but the process is the same for any email type. By the end, you will have an email ready to send.
{% endhint %}
{% stepper %}
{% step %}
### Add the email from the campaign page
From the campaign page, click **Add Component**, then **Email**.
{% endstep %}
{% step %}
### Fill in settings, choose a template, create the email
**Settings**
* **Name your email:** Give the email a unique name so you can find it later. Describe the email's purpose in the context of the campaign — for example, "Invitation" for an invitation email. Only you see this name; it is not shown to your contacts.
* **Subject:** The subject line recipients see in their email clients.
* **From Name:** The sender name shown in recipients' email clients.
* **From Address:** This has two parts that make up the sending address.
1. The part before the `@` can be almost anything. If you are not sure, `noreply` works for most cases, though a real inbox that can receive replies is preferred.
2. The part after the `@` is your email domain. You must add your own domain before you can send. See [Add Email domain](/getting-started/account-setup/authorize-email-domain.md) for how.
* **Reply-to Address (optional):** An address that receives any replies, useful if the From Address cannot receive email. Rarely used; usually safe to skip.
* **Subscription Category (optional):** If your account uses subscription lists, you can categorize this email here. Rarely used; usually safe to skip.
**Template**
Pick a template from one of the tabs as a starting point for the design. This guide uses **Hero Event** from the **Events** tab. Custom templates saved on your account appear under **My Templates**.
{% hint style="info" %}
Every email starts from a template, so you can't create one without a template. To start from a blank design, choose **Empty email** on the **Layouts** tab. It starts empty, and all the content blocks for emails are available to add.
{% endhint %}
**Create email component**
Once settings and template are set, click **Create** to create the component.
{% endstep %}
{% step %}
### The email editor
After you click **Create**, the editor opens with the new email. The left-side menu lets you add content blocks, access tools, and update the settings from the previous step. The rest of the page shows the email content, imported from the template you chose.
The content is made up of content blocks, which you edit individually in the following steps.
{% endstep %}
{% step %}
### Edit a content block
Each content block is made up of several parts you can update. Click the block's edit button to open its settings.
A settings menu opens on the right with two tabs: **Content** and **Styles**. Content is where you change the block's settings and content. Styles is where you change colors and fonts.
On the Content tab, the first section controls how the block displays — leave those defaults for now. The second section is what appears in the block: images, headlines, text paragraphs, and buttons.
{% endstep %}
{% step %}
### Change a block's headline
To change a headline or text paragraph, click the title bar for that part and edit the text in the text box. If you leave the text box empty, that part of the block is hidden.
In the image below, we are not using the text paragraph and two of the link buttons, so they do not appear in the email.
Click **Save** after each change to save your work.
{% endstep %}
{% step %}
### Upload an image
To upload your own image, open the content block for editing, go to the Image section in the right-side menu, and click **Choose Image**.
The Choose Image button
To upload and use an image:
1. Click **Upload Files**.
2. Click **Choose files** and select the image on your computer.
3. Upload the file to your eMarketeer account.
4. Click the file in the browser window to select it.
5. Click **Use Selected** to add it to the content block.
If the image does not match the recommended dimensions for the block, an option to auto-scale it appears. Click the link in the notice to accept.
{% endstep %}
{% step %}
### Add a button with a link
Use buttons to link to a webpage, file, or another eMarketeer component. For a web link, type the URL in the Link settings (include the `http://` or `https://` protocol) and write a button caption. To link to another eMarketeer component, follow these steps:
1. Open the "Link 1" content settings and click **Browse**.
2. Click **eMarketeer Form**.
3. Pick the campaign that contains your form in the first dropdown, then the form in the second dropdown.
4. Click **Select**, then **Apply**, then **Save** to add the link and save the block.
{% endstep %}
{% step %}
### Add a new content block
To add a new content block, click **Add Content Block** in the left-side menu. In the Add Content menu on the right, click **Add Block** next to the type you want.
If the button is grey, first click an existing block to tell the editor where the new one should go.
{% endstep %}
{% step %}
### Reposition a content block
To move a block, click and hold the reposition icon on the left side of the block's context bar, then drag it to the new position.
{% endstep %}
{% step %}
### Delete a content block
To remove a block from the template, click the delete button on its context bar.
{% endstep %}
{% step %}
### Use a block with a calendar link
Some content blocks support a calendar link feature, which is useful for events. When a recipient clicks the link, eMarketeer generates a calendar file that adds the event to their calendar using the settings you chose.
You configure the calendar event in the block's content menu — date, time, title, location, and so on.
Keep the **Description** field to plain text and limit it to two or three short paragraphs.
{% endstep %}
{% step %}
### Add a preheader and finish the email
The Email Settings block at the top of most emails is optional. Most of its settings are for special use cases involving shared links to the email content, but the **Preheader** is worth using.
The preheader is the short summary that recipient email clients show next to the subject line. Use it to summarize what the email contains.
Once your preheader is saved, click **Done Editing** to exit the editor.
{% endstep %}
{% endstepper %}
### What to do next
The email is ready to send. See [How to send an email](/getting-started/campaign-basics/basics-send-email.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.emarketeer.com/getting-started/campaign-basics/basics-creating-email.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
