> 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/help-and-faqs/how-to-change-elements-of-page/homepage.md).

# How do I change the sections on my homepage?

The homepage is the page most visitors land on, and it is the page with the most sections in it. It is also the easiest place to learn how the theme editor is put together: once you know how to find and edit a section here, the same routine works on every other page.

This page is the entry point to the homepage maps. A map is a numbered screenshot of the demo homepage, top to bottom, where every number links to the page that documents that section's settings.

### Homepage maps <a href="#homepage-maps" id="homepage-maps"></a>

* [**Vélare**](/velare/help-and-faqs/how-to-change-elements-of-page/homepage/velare.md): the section map for the Vélare homepage. Scroll through the numbered screenshots, find the block you want to change, and open the link next to its number.

### How to use a map <a href="#how-to-use-a-map" id="how-to-use-a-map"></a>

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

1. Open your storefront and scroll to the block you want to change.
2. Open the [Vélare map](/velare/help-and-faqs/how-to-change-elements-of-page/homepage/velare.md) and find the same block in the numbered screenshots.
3. Click the link next to its number to read what each of its settings does.
4. Go to **Online Store > Themes > Customize**, click that section in the left sidebar, and make the change.
5. Click **Save**.
   {% endhint %}

*Result:* the preview updates as you edit, and the change goes live on your storefront as soon as you save.

{% hint style="info" %}
Your homepage will not match the demo exactly if you started from a different preset or removed sections during setup. The numbering is a guide to what the theme can show, not a list of what your store currently shows.
{% endhint %}

### When to contact support <a href="#when-to-contact-support" id="when-to-contact-support"></a>

Contact support when a block on your homepage does not match anything on the map, or when a section is on the map but missing from your section list.

Send this with your first message:

* Your store URL.
* A screenshot of your homepage with the block circled.
* The number of the block on the map, if you found something close.
* Theme name and version: **Vélare 1.0.0**, shown under the theme name in **Online Store > Themes**.

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

* [Vélare](/velare/help-and-faqs/how-to-change-elements-of-page/homepage/velare.md): the numbered homepage map
* [How to change Elements of page?](/velare/help-and-faqs/how-to-change-elements-of-page.md): the parent group, and how to open the theme editor
* [Staff account](/velare/help-and-faqs/staff-account.md): how to give the support team access to your store


---

# 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/help-and-faqs/how-to-change-elements-of-page/homepage.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.