> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/building-interactive-demos/tour-centers/mobile-optimization.md).

# Mobile Optimization

Optimize your Tour Center for mobile devices

1. From the Tour Center editor, click "Tour Center Overview"
2. Toggle on "Show on Mobile"
3. You'll see toggles next to each piece of content in the "Content" section below, giving you control over what is displayed when the Tour Center is viewed on a mobile device. If a tour is not mobile optimized, that will be indicated a![](https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FWSutybOPz83szLR32vWr%2Fimage.png?alt=media\&token=57dea138-0aa1-4737-b5d0-ce0780b9526a)icon.
   1. NOTE: If you toggle off a piece of content in the mobile view, be sure there is still some content in the respective Content Track. You will not be able to publish your Tour Center if a Content Track is empty.&#x20;
4. Once you've made your changes, click Publish.

<figure><img src="https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FvpAtxMDLpX5dD3geNOaP%2F6814caf17766c5c0551505c5.gif?alt=media&amp;token=d6c089b6-3f83-49f4-9f7f-3ca6f5291a03" alt=""><figcaption></figcaption></figure>


---

# 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://docs.navless.ai/building-interactive-demos/tour-centers/mobile-optimization.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.
