> For the complete documentation index, see [llms.txt](https://docs.lufavo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lufavo.com/roomfolk/sections/email-signup.md).

# Email signup

A closing panel with a headline and an email field — the newsletter signup. It can sit on a flat color or over a photograph.

In the theme editor this section is called **Email signup**.

## Set it up

1. Add the section, or find it near the bottom of the home page.
2. Write a headline and a line explaining what people are signing up for.
3. Optionally add a background image.

## Content

| Setting      | What it does                  |
| ------------ | ----------------------------- |
| Kicker       | Small line above the heading. |
| Heading      | The headline.                 |
| Heading size | Small, Medium or Large.       |
| Description  | A sentence or two under it.   |

Say what people are signing up for and how often. "Never more than one email a month" earns more signups than "Subscribe to our newsletter".

## Email signup

| Setting             | What it does                                               |
| ------------------- | ---------------------------------------------------------- |
| Signup note         | An optional line under the field.                          |
| Signup button label | The button text. Leave blank to use the theme translation. |

**Where the addresses go.** Signups are added to your Shopify customer list, marked as accepting marketing. You will find them under **Customers** in your admin, and you can send to them from Shopify Email or export them. No app is needed, and nothing is stored by the theme.

## Image

| Setting              | What it does                                       |
| -------------------- | -------------------------------------------------- |
| Image                | An optional background photograph.                 |
| Mobile image         | An optional tighter crop for narrow screens.       |
| Image fade           | 0% to 100%. Fades the image toward the page color. |
| Image fade on mobile | The same, for narrow screens.                      |

**There are two fade settings because phones need more.** The text sits over a narrower slice of the image on a phone, so it usually needs more fading to stay readable — which is why the mobile default is higher than the desktop one.

The fade is drawn in the scheme's own background color, not in black, so it works on a light scheme and a dark one without you changing anything.

## Layout, spacing and style

| Setting          | What it does                                         |
| ---------------- | ---------------------------------------------------- |
| Content position | Left, Center or Right.                               |
| Alignment        | How the text is aligned within that area.            |
| Top spacing      | 0px to 120px.                                        |
| Bottom spacing   | 0px to 120px.                                        |
| Color scheme     | Which scheme the section uses. Defaults to scheme 4. |

## Also used for the password page

This section is what fills your password page while the store is locked. See [Password page](/roomfolk/pages/password-page.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 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://docs.lufavo.com/roomfolk/sections/email-signup.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.