> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/app/navigation.md).

# Navigation

Navigation Overview

The **Navigation** category provides resources to help you configure and manage the navigational elements of your app. This section focuses on creating an intuitive user experience by guiding you through the setup of **bottom navigation** and **side menus** while also offering solutions to common issues.

<figure><img src="https://3330324049-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxUo90vXzDtbgOtaUaLYv%2Fuploads%2F690IEVX5vIrIbDYVLOxl%2FNavigations.png?alt=media&amp;token=ee19076d-78ea-4205-ab7d-fd0df71a702e" alt=""><figcaption></figcaption></figure>

Here’s what you’ll find in this category:

* [**B**ottom Navigation Setup](https://docs.appmysite.com/app/navigation/bottom-bar.md): Step-by-step guides to configure and customize the bottom navigation bar, including adding and managing items, icons, and layouts.
* [Side Menu Configuration](https://docs.appmysite.com/app/navigation/menu.md): Tutorials on creating and personalizing side menus to enhance app navigation and accessibility.
* Troubleshooting Navigation Issues: Solutions to common problems related to navigation elements, ensuring a smooth and seamless user experience.

Explore the Navigation category to optimize your app’s structure and provide users with a streamlined and efficient way to navigate your app.


---

# 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.appmysite.com/app/navigation.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.
