> 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.md).

# Forms

**Forms** is the group of sections that collect something from a visitor rather than sell to them. Today that means the newsletter signup, the one place on a page where a shopper who is not ready to buy can still leave you a way to reach them later. Shoppers meet these sections low on the homepage or on a landing page, after the products have made their case.

Use this group when you want a signup that lives in the flow of the page. For a signup that interrupts the visit instead, see the [Newsletter popup](/velare/customize-your-pages/overlay-group/newsletter-popup.md) in the overlay group.

### Where to find it <a href="#where-to-find-it" id="where-to-find-it"></a>

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

1. Go to **Online Store > Themes > Customize**.
2. Open the template where the form should appear, for example the homepage.
3. Click **Add section**.
4. Open the **Forms** group and choose the section you need.
5. Write the heading and the button label, then drag the section into position.
   {% endhint %}

*Result:* the form renders in place, and addresses submitted through it arrive in your Shopify admin under customers.

### Sections in this group <a href="#sections-in-this-group" id="sections-in-this-group"></a>

| Section                                                        | What it does                                                                       | Use it when                                                                    |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| [Newsletter](/velare/customize-your-pages/forms/newsletter.md) | An email signup with a heading, a description, an email field, and a submit button | You want visitors to be able to subscribe without a popup getting in their way |

### Suggested reading order <a href="#suggested-reading-order" id="suggested-reading-order"></a>

1. Decide what shoppers get in return for their address before you write anything. A signup with no stated benefit is the most common reason these forms sit empty.
2. Read [Newsletter](/velare/customize-your-pages/forms/newsletter.md) and pay particular attention to the placeholder and button label, since those two lines do most of the persuading.
3. Check your email marketing tool is connected in the Shopify admin, otherwise addresses are collected but never used.

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

* [Newsletter](/velare/customize-your-pages/forms/newsletter.md): the only section in this group
* [Newsletter block](/velare/customize-your-pages/forms-1/newsletter.md): the block version, for a signup inside another section
* [Newsletter popup](/velare/customize-your-pages/overlay-group/newsletter-popup.md): the same signup as an overlay
* [Contact form](/velare/customize-your-pages/forms-1/contact-form.md): for messages rather than subscriptions


---

# 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.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.