> 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.md).

# How do I change the sections on a page?

Everything customers see on your store is built from **sections** you can move, edit, or remove yourself in the Shopify theme editor. Nothing here needs code.

This group answers the question merchants ask most often after installing Vélare: *"I can see this block on my store, where exactly do I click to change it?"* Each page below is a map: you look at the screenshot, find the block you want to edit, and follow the link to the page that documents its settings.

### Open the theme editor first <a href="#open-the-theme-editor" id="open-the-theme-editor"></a>

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

1. Log in to your **Shopify admin**.
2. Go to **Online Store > Themes**.
3. In the **Current theme** area, find the theme you are using and click **Customize**.
   {% endhint %}

*Result:* the theme editor opens with a preview on the right and the list of sections on the left. That list is what the maps below refer to.

### Pages in this group <a href="#pages-in-this-group" id="pages-in-this-group"></a>

* [**Homepage**](/velare/help-and-faqs/how-to-change-elements-of-page/homepage.md). **Start here.** The homepage carries the most sections, so it is the fastest way to learn how the editor is organised.
  * [**Vélare**](/velare/help-and-faqs/how-to-change-elements-of-page/homepage/velare.md): the numbered map of every section on the Vélare demo homepage, with a link to the settings page for each one.

{% hint style="info" %}
Other pages (collection, product, blog, cart, contact) are documented in their own groups rather than here. If you cannot find a block on the homepage map, it probably belongs to one of those page templates.
{% endhint %}

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

Contact support when a block you can see on your storefront does not appear anywhere in the section list, or when a section refuses to move or delete.

Send this with your first message so nobody has to ask for it:

* Your store URL, and the URL of the page where you see the block.
* A screenshot with the block circled.
* Theme name and version: **Vélare 1.0.0**, shown under the theme name in **Online Store > Themes**.
* A [staff account](/velare/help-and-faqs/staff-account.md) for the support team, if you want them to look inside the editor themselves.

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

* [Homepage](/velare/help-and-faqs/how-to-change-elements-of-page/homepage.md): the section map for the homepage
* [Header](/velare/set-up-your-store/header-group/header.md): the navigation bar shown on every page
* [Footer](/velare/set-up-your-store/footer-group/footer.md): the block at the bottom of every page
* [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.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.