> For the complete documentation index, see [llms.txt](https://highfivethemes.gitbook.io/reflect-user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://highfivethemes.gitbook.io/reflect-user-documentation/custom-settings/subscribe-cta-banner.md).
# Subscribe CTA Banner
**Reflect** supports adding and customizing Subscribe CTA Banner on your publication's homepage. There are 3 settings for this**:**
1. **Subscribe CTA text**
2. **Subscribe CTA subtext**
3. **Subscribe CTA position**
## Subscribe CTA text
This setting is responsible for big main CTA text in the banner.
## **Subscribe CTA subtext**
This setting is responsible for smaller text, which is above the email input.
## **Subscribe CTA position**
This setting is responsible for the position of the banner. Just enter the section position (**1** or **2** or **3** or **4**) after which you would like to display the banner.
{% hint style="info" %}
To remove Subscribe CTA Banner just delete it's position number from the **Subscribe CTA position** setting.
{% endhint %}
## **To customize:**
* Go to **Settings > Design & branding** from the admin menu
* Click **Homepage** in the **Design** settings sidebar on the right
* Enter your CTA text in text inputs inside **Subscribe CTA text** and **Subscribe CTA subtext** settings
* Enter your preferred banner's position in **Subscribe CTA position** setting
---
# 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://highfivethemes.gitbook.io/reflect-user-documentation/custom-settings/subscribe-cta-banner.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.
.png?alt=media&token=ee6222a0-cafa-473b-919f-8cfe7efc163e)
