# Navigation Most apps need an interface that lets users navigate their app. Navigation can mean many things, such as: * Including a header, sidebar or footer with buttons or links that take you to a different part of the page or to another page * Links in text elements that takes the user to an external page * Buttons that take the user to a new section, such as the next step in a form ## Single-page and multi-page navigation App navigation are split into two types: **Single-page apps** are apps that navigate without leaving or reloading the page, by dynamically hide and show containers and elements based on the user's actions. **Multi-page apps** are apps that navigate by sending the user to different pages. What method to use is not necessarily a black-and-white question: most applications use a mix between the two, where some features are placed on a larger single-page navigation page, whereas others are placed in isolation on separate pages. {% content-ref url="/pages/olN0hwlEeKT8tmw6cZUN" %} [Single-page applications (SPA)](/help-guides/logic/navigation/single-page-applications-spa.md) {% endcontent-ref %} {% content-ref url="/pages/BWRr5D7QRnPTlOO7cCnp" %} [Multi-page applications](/help-guides/logic/navigation/multi-page-applications.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://manual.bubble.io/help-guides/logic/navigation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.