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

# Page tabs

Add a screen with tabs displaying different content

Toggle content inside a page without needing to replicate screens. Page tabs can be used either as an extra navigational hierarchy that complements the main bottom menu or you can also use it to navigate content with buttons inside a page.

<figure><img src="https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXpqEanvOhm8vMtIH8i%2Fuploads%2F7f689W8aWa5qkNPfyJGG%2FScreen%20Recording%202022-12-07%20at%2010.16.52.gif?alt=media&amp;token=adcfa8a5-7249-47ba-a883-38a1bdbc38ae" alt=""><figcaption></figcaption></figure>

## 👉 **The Tags**

This component requires the following tags:

* <mark style="color:red;">**`[container:tabs]`**</mark>: this tag creates a special [container](/set-up-design/setting-up-your-design-file/the-container.md) element, wrapping up both the tabs control and the content of the segmented tabs. It needs to be added in the [**2nd level laye**](/set-up-design/setting-up-your-design-file/structuring-the-design-the-layer-hierarchy.md)**r** in the design file and its size shouldn't be bigger than the main screen.
* <mark style="color:red;">**`[container:tabs-controls]`**</mark>: a special container inside the <mark style="color:red;">`[container:tabs]`</mark> element. It will contain the tabs controller to switch between the different segmented tabs. It needs to be aded in the [**3rd level layer**](/set-up-design/setting-up-your-design-file/structuring-the-design-the-layer-hierarchy.md) in the design file.
* <mark style="color:red;">**`[container:tabs-content]`**</mark>: a special container inside the \[container:tabs] element. It will be used for the content for the segmented tabs. It needs to be aded in the [**3rd level layer**](/set-up-design/setting-up-your-design-file/structuring-the-design-the-layer-hierarchy.md) in the design file.

## 🎨 Design setup

1. Create the tabs controller, using a [stateful component](/bravo-tags/components/stateful-component-like-button.md) to create the buttons and different states (default and active). Create a <mark style="color:red;">`[container:tabs-controls]`</mark> around the buttons.
2. Create a frame that takes the space for the segmented tabs content. Add the <mark style="color:red;">`[container:tabs-content]`</mark> tag in this element.
3. Surround all these elements with a <mark style="color:red;">`[container:tabs]`</mark> element, located in the second-level layer.

<figure><img src="https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXpqEanvOhm8vMtIH8i%2Fuploads%2FQN4SQkHqY56trZkPtBFH%2Fimage.png?alt=media&amp;token=186f9f1a-b9e0-4f86-8886-bcbd4d6bc0fc" alt=""><figcaption></figcaption></figure>

4\. Finally, to create the content for the segmented tabs, create separate screens with the content you want to display, and create prototyping links from the buttons in the controller to these pages. You can [bind API data](/data-binding/data-binding-types.md) to the pages as well.

<figure><img src="https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXpqEanvOhm8vMtIH8i%2Fuploads%2FDkjr3aF7iQlYMcB2eCUS%2Fimage.png?alt=media&amp;token=9baf8905-6294-4333-aa0b-3f8833c52f64" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Please note that the `refresh:pull` tag is currently not supported within a Tabs Container on Android devices.
{% endhint %}

## 💾 Example file

Duplicate this file below to see how to set it up!

{% embed url="<https://www.figma.com/community/file/1182258624876265324>" %}


---

# 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.bravostudio.app/bravo-tags/pages/page-tabs.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.