> 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/header-and-navigation/mobile-dock.md).

# Mobile dock

A fixed bar at the bottom of phone and tablet screens, with up to six links such as menu, search, cart, and account.

The dock holds up to six destinations: home, menu, search, cart, account, news, and your own links.

{% hint style="info" %}
**Theme Editor → Mobile dock**
{% endhint %}

The dock is already in the theme. It is not under **Add section**, and it cannot be moved to another template. It shows on screens up to 920px wide, where the desktop header and sidebars are hidden. Switch the preview to mobile to see it.

To turn the dock off, remove all of its blocks. An empty dock renders nothing.

***

{% stepper %}
{% step %}

#### **Add the blocks**

Add up to 6 blocks and drag them into order.

**Home**, **Menu drawer**, **Search**, **Cart**, **Account**, and **News** can each be added once. **Link** is a custom icon, title, and URL, and it can be added more than once, still inside the limit of 6.
{% endstep %}

{% step %}

#### **Choose how the blocks look**

**Display** is **Icon and text**, **Icon**, or **Text**. A block with no icon and no title is skipped.

**Sticky dock** is **Always**, **On scroll to top**, or **Disabled**. **Always** pins the bar to the bottom. **On scroll to top** shows it when the visitor scrolls up. **Disabled** places it after the footer, in the page flow.

**Highlight current page** marks the block for the page the visitor is on.
{% endstep %}
{% endstepper %}

***

#### **Good to know**

**Menu drawer** opens the menu drawer or the mega menu drawer, depending on the menu style in theme settings.

**Search** opens quick search. When quick search is off, the block links to the search page.

**Cart** opens the cart in the mode set for the theme, with an item count. The block is removed when shopping is disabled in theme settings.

**Account** opens the account dialog. **News** opens the news drawer. The links inside the account dialog come from the Account block's own **Account menu** setting; when it is left empty, the theme falls back to **Theme settings → Customer accounts → Menu**.

Chat bubbles, cookie banners, and other fixed widgets are not moved out of the way. Only the sticky Add to cart bar, the Quick order list footer, and the search-results toast account for the dock height. Set the offset in that app.

The dock does not render on the password page.

***

#### **Common issues**

<details>

<summary>A block is missing in the preview</summary>

The block has no icon and no title, or **Display** is set to the part the block does not have. **Cart** is also hidden when shopping is disabled in theme settings.

</details>

<details>

<summary>On scroll to top never appears</summary>

The bar stays hidden until the visitor scrolls up. On a page that does not scroll, it never appears. Use **Always** on short pages.

</details>


---

# 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/header-and-navigation/mobile-dock.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.
