> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/channels/email/email-templates/default-template.md).
# Default Template
An introduction to the default template.
Every UbiQuity account comes with a Default Easy Edit template — a base EasyEdit template that is pre-configured and ready to use. The following pages document the Default Easy Edit template in detail.
**Field Types**\
Email Easy Edit offers a variety of field types to customise your email content. Understanding these field types is crucial for creating engaging and dynamic emails. Here are the primary field types you will encounter.
**Base Settings**\
The settings section allows you to configure various aspects of your email. These settings ensure that your email aligns with your branding and communication goals.
**Article Blocks**\
Article blocks are the building blocks of your email content. They allow you to structure your email in a visually appealing and organised manner.
**Layouts**\
Layouts provide predefined structures for your email, making it easier to design professional-looking emails quickly. You can choose from various layouts to suit your content needs.
By understanding and utilising these field types, settings, article blocks, and layouts, you can create compelling and effective emails that resonate with your audience. Dive into the following sections for detailed instructions and tips on using each feature to its fullest potential.
The default Easy Edit template available in all accounts.
---
# 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://docs.ubiquity.co.nz/documentation/channels/email/email-templates/default-template.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.
