> 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/customize-your-pages/about-us.md).

# About us

The **About us** page is where you tell shoppers who is behind the store: your story, how the products are made, and why they should trust you. Visitors reach it from the header menu or the footer, usually before a first order when they are still deciding whether the store is real and worth buying from. Because it is built from theme sections, you can present the story with images, text, and even a product row instead of one long paragraph.

Unlike the 404 or cart templates, this page does not exist until you create it. You create a page in the Shopify admin, attach a theme template to it, then arrange the sections in the theme editor.

<figure><img src="/files/WSSvdIY5chkHTIK0OJBv" alt=""><figcaption></figcaption></figure>

### Step 1: Create the page in the Shopify admin <a href="#step-1-create-the-page" id="step-1-create-the-page"></a>

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

1. Go to **Shopify admin > Online Store > Pages**.
2. Click **Add page**.
3. Fill in:
   * Title: `About us`
   * Visibility: **Visible**
4. In **Theme template**, select `about`.
5. Click **Save**.
   {% endhint %}

*Result:* the page now exists at an address such as `/pages/about-us` and uses the theme template instead of the plain default one.

### Step 2: Arrange the sections <a href="#step-2-arrange-the-sections" id="step-2-arrange-the-sections"></a>

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

1. Go to **Online Store > Themes > Customize**.
2. Open the template selector and choose **Pages**, then your About us page.
3. Add, remove, or reorder the sections in the left sidebar.
4. Click **Save**.
   {% endhint %}

*Result:* the preview shows the story layout that visitors will see, with the header and footer already in place around it.

### What is on this page <a href="#what-is-on-this-page" id="what-is-on-this-page"></a>

* [Page template sections](/velare/customize-your-pages/about-us/page-template-sections.md): the sections the theme adds to this template by default, and where to read about each one.

### Add the page to your navigation <a href="#add-the-page-to-navigation" id="add-the-page-to-navigation"></a>

A new page is not linked from anywhere until you add it to a menu. Add it to your main menu in **Online Store > Navigation** if you want it in the header, or to a footer menu if it belongs with your policy links.

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

* [Contact page](/velare/customize-your-pages/contact-page.md): the page visitors open next when the story convinces them to get in touch
* [Page](/velare/customize-your-pages/page.md): the title block shown at the top of pages like this one
* [Footer](/velare/set-up-your-store/footer-group/footer.md): where an About link usually sits alongside the policy links


---

# 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/customize-your-pages/about-us.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.
