> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/customize-your-pages/forms-1.md).

# Forms

The **Forms** blocks are the two places shoppers can type something back to you. They are added inside a section rather than placed on a page by themselves, which means a signup box or an enquiry form can sit in the middle of a story, under a picture, or at the end of a page instead of being a section of its own.

Both blocks are built from placeholder wording and a button label, so most of the work is deciding what to ask for. Ask for less and more people finish.

### How to add a form block <a href="#how-to-add" id="how-to-add"></a>

{% hint style="success" %}
**Steps:**

1. Go to **Online Store > Themes > Customize**.
2. In the left sidebar, click the section that should carry the form.
3. Click **Add block**.
4. Choose **Contact form** or **Newsletter**, then set the field wording and the button label.
   {% endhint %}

*Result:* the form appears inside the section in the preview, with the placeholder wording you entered.

### Blocks in this group <a href="#blocks-in-this-group" id="blocks-in-this-group"></a>

| Block                                                                | What it asks shoppers for                                                                   | Reach for it when                                                           |
| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- |
| [Contact form](/velare/customize-your-pages/forms-1/contact-form.md) | Name, email, phone, a dropdown choice, and a message, with any field you leave empty hidden | Shoppers need to send a question, a wholesale enquiry, or a support request |
| [Newsletter](/velare/customize-your-pages/forms-1/newsletter.md)     | An email address only                                                                       | You want to build a marketing list without interrupting the page            |

### Choosing between them <a href="#choosing-between-them" id="choosing-between-them"></a>

1. Use [Newsletter](/velare/customize-your-pages/forms-1/newsletter.md) anywhere on the store where signing up is a side offer, since a single field costs shoppers almost nothing.
2. Use [Contact form](/velare/customize-your-pages/forms-1/contact-form.md) on the pages people arrive at with a question already in mind, such as contact, support, or wholesale.
3. On the contact form, leave the placeholder empty for any field you do not need. The field disappears rather than sitting there unlabelled.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Google maps](/velare/customize-your-pages/decorative/google-maps.md): the location block that usually sits beside a contact form
* [Basic](/velare/customize-your-pages/basic.md): the heading and wording that explain what happens after shoppers submit
* [Layout](/velare/customize-your-pages/layout.md): the containers for placing a form next to other content


---

# 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 dynamically by asking a question.

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

```
GET https://uxsmart.gitbook.io/velare/customize-your-pages/forms-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.