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

# Pages

- [Modal pages](https://docs.bravostudio.app/bravo-tags/pages/modal-pages.md): Pages that slides in from the bottom and covers the screen.
- [Pop-up pages](https://docs.bravostudio.app/bravo-tags/pages/pop-up-pages.md): Pop-up pages can be effective for drawing attention to specific information or encouraging user interaction.
- [Swipe page](https://docs.bravostudio.app/bravo-tags/pages/swipe-page.md): Add a component with a vertical swipe effect
- [Transitions page](https://docs.bravostudio.app/bravo-tags/pages/transitions-page.md): Transitions are used to create a smooth and visually appealing flow between different views or states of an app, enhancing the overall user experience.
- [Page reveal animations](https://docs.bravostudio.app/bravo-tags/pages/page-reveal-animations.md): Refers to an animated effect where content or elements gradually become visible on the screen, often in response to a user interaction.
- [Page tabs](https://docs.bravostudio.app/bravo-tags/pages/page-tabs.md): Add a screen with tabs displaying different content
- [Stateful pages](https://docs.bravostudio.app/bravo-tags/pages/stateful-pages.md)


---

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