> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/global-sections/footer-group.md).

# Footer group

Sections inside the footer group: Footer layout and column settings, Footer reveal, Popup modal for promotions, Flyout slide-in panel, and the Age verification gate.

The footer group contains sections that appear globally across your store. This includes the site footer itself, as well as promotional overlays — Popup and Flyout — and the Age verification gate, which are configured here even though they appear as floating elements on top of your content.

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2Fz8K2E4qOBwzeU6fzVf3A%2FGroup%2013%20(4).jpg?alt=media&amp;token=aa659fda-b738-4b69-bfd8-27a2e3e915d1" alt=""><figcaption></figcaption></figure>

| Section                                                                                  | What it does                                                                                                      |
| ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Footer](/docs/avante-themes/global-sections/footer-group/footer.md)                     | Multi-column footer with menus, text blocks, newsletter, social icons, and payment icons                          |
| [Footer reveal](/docs/avante-themes/global-sections/footer-group/footer-reveal.md)       | Full-width image or video at the bottom of the store, with a logo and up to three blocks of content over it       |
| [Popup](/docs/avante-themes/global-sections/footer-group/popup.md)                       | Modal overlay for promotions, newsletter signups, and discount codes — triggered by timer, scroll, or exit intent |
| [Flyout](/docs/avante-themes/global-sections/footer-group/flyout.md)                     | Slide-in panel with a persistent tab on the page edge for promotions and announcements                            |
| [Age verification](/docs/avante-themes/global-sections/footer-group/age-verification.md) | Full-screen age gate with accept and decline buttons, shown before the store can be browsed                       |

All sections in this group are configured in the **Footer group** in the Theme Editor (Customize → Footer).

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FMiUi33gHa4pJ8vjYBmhe%2FGroup%2013%20(5).jpg?alt=media&amp;token=e0c3ae8a-470c-4964-b617-300dfd18f7a8" alt=""><figcaption></figcaption></figure>


---

# 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://staylime.com/docs/avante-themes/global-sections/footer-group.md?ask=<question>&goal=<user_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.
