> For the complete documentation index, see [llms.txt](https://help.inveterate.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.inveterate.com/help-center/guides/program-setup/landing-page/configuring-the-landing-page/hero.md).

# Hero

**Content** 

1. Enter the title for your program, this should be a unique and branded membership name
2. Enter the subtitle.  This is body copy that gives your customers an overview of what they can expect from signing up for your membership program.
3. Enter the sign up CTA.  This is the copy that will appear inside of the CTA button that users click to sign up for your membership program.

**Design**

1. Select a background color for the hero module.  This color will appear behind all of your text.
2. Select your text color.  Make sure this color is legible against your background color.
3. Select your Primary Button background color.  This is the color of your CTA button.
4. Select your Primary Button text color.  This is the color of the text inside your CTA button.
5. Select your Secondary Button background color.  This is the color of the Login link.

#### Download the PDF below for step-by-step instructions

{% file src="/files/A4O31uGtkKQvNcMs8jCv" %}


---

# 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://help.inveterate.com/help-center/guides/program-setup/landing-page/configuring-the-landing-page/hero.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.