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

# Mobile Header

Configure the Avante mobile header: logo, hamburger menu, search, cart icon, and mobile-specific navigation layout.

A separate header section designed specifically for mobile screens. Unlike many themes that simply shrink the desktop header, Avante gives you full control over the mobile navigation — its own logo, layout, and set of elements.

***

### How to find

**Theme Editor → Mobile header** — near the top of the section list, just below the desktop Header, on every page.

Mobile Header is independent from the desktop [Header](https://staylime.com/docs/avante-themes/global-sections/header-and-navigation/header.md). Changes to one do not affect the other.

***

### Logo

The Mobile Header has its own Logo block. By default it uses the same image as the desktop header, but you can set a different logo height to better fit the smaller screen — the desktop header's **Logo height** has no effect here.

You can also switch the logo to **text mode** — useful if your image logo doesn't scale well on mobile.

[**Enlarged logo**](https://staylime.com/docs/avante-themes/global-sections/header-and-navigation/header.md#enlarged-logo) works here the same way as on the desktop header: **Enlarge logo**, **Show on** (**Home page only** / **All pages**), **Size** (110–300%, default 200) and **Offset** (0–100 px). It is set on this section’s Logo block, separately from Header and Secondary header. See Header → Enlarged logo.

***

### Miscellaneous

Controls the icons and elements displayed in the mobile header bar — search, account, cart, and burger menu. The key setting worth noting:

**Reverse order** — flips the position of elements in the header. If your burger menu is on the left and cart on the right by default, enabling this swaps them. Handy for matching the layout conventions your audience expects.

***

### Buttons

You can add up to two custom buttons directly in the mobile header — for example, a "Call us" or "Book now" link. Each button supports an icon, label, link, and style (solid, outlined, or text link).

{% hint style="success" icon="sparkles" %}
**Tip:** On mobile, screen space is limited. Use a single button with an icon and no label for a clean look — for example, a phone icon linking to `tel:+1234567890`.
{% endhint %}

***

### Sticky header

Same options as the desktop header, set separately:

| Option           | Behavior                                     |
| ---------------- | -------------------------------------------- |
| Disabled         | Header scrolls away with the page            |
| On scroll to top | Header reappears when the visitor scrolls up |
| Always           | Header stays pinned at the top               |

**On scroll to top** is the recommended option for mobile — it keeps the header accessible without permanently taking up screen space.

***

#### Related

* [Header](https://staylime.com/docs/avante-themes/global-sections/header-and-navigation/header.md) — desktop navigation bar
* [Menu Drawer](https://staylime.com/docs/avante-themes/global-sections/header-and-navigation/menu-drawer.md) — slide-out mobile menu (opens from the burger icon)
* [Appearance settings](https://staylime.com/docs/avante-themes/theme-settings/appearance.md) — navigation layout options


---

# 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-header.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.
