# Getting started with Taxi Email Design Systems

In Taxi for Email, when we talk about an Email Design System, we're referring to the structure of your email.

An Email Design System is a normal HTML email, with Taxi Syntax added so that you can edit blocks of the email without changing the code. This allows anyone in an organisation to edit the email, regardless of their knowledge of code in emails.&#x20;

Each Taxi account comes with a built-in Email Design System that you can use. You can also upload your own, or have them built using our Email Design System Service. All the Email Design Systems are live in your account under the 'Email Design Systems' tab.

Each Email Design System is made up of a number of modules, which you can add to your mailing. A mailing starts off blank, and you can add modules to an email. Modules contain elements, such as a text field, which you can then input content into.

When setting up a new mailing, you select an Email Design System to apply to it. It becomes the Email Design System for this mailing.

Read next:&#x20;

[Built-in Email Design Systems](/taxi/email-design-systems/built-in-taxi-email-design-systems.md) | [Custom built Email Design Systems](/taxi/email-design-systems/custom-email-design-systems.md) | [Creating and managing mailings](https://docs.messagebird.com/taxi/Projects,%20Mailings%20and%20Versions/Mailings/creating-and-managing-mailings)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/taxi/email-design-systems/email-design-systems/getting-started-with-taxi-email-design-systems.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
