> For the complete documentation index, see [llms.txt](https://docs.openbuild.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbuild.io/working-with-the-framework/navigation/navigation-through-url-parameters.md). # Navigation through URL parameters A more advanced way of navigating is to use URL parameters. These have two distinct advantages over custom states: a) when you use url parameters, you still navigate by the URL even if you do not seem to leave the page. This means you build up a breadcrumb trail and can go back and forth in the browser to go to a previous page. B) you can append parameters to your URL's that can interact with your page as you navigate. You can add a URL parameter in a link in your emails to navigate to the right section of your page for example. In general passing data along in URL parameters is a common practice and very versatile.

Set type of content for the section as 'text' and type in the text you want to refer to when navigating

We are referring the URL parameter to make the right section visible

Navigation action can refer to the text on the ❖ Section Users we set. The workflow will look like this:

Additionally, you can use extra parameters such as 'tab' to create a sub-navigation. Or UID if you are working with data (read more about this in [this section](/working-with-the-framework/data-and-workflows/crud.md)). You can also use more advanced practice such as using Option set to navigate. You can read about it in the [next section](/working-with-the-framework/navigation/navigation-through-url-parameters-with-option-sets.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openbuild.io/working-with-the-framework/navigation/navigation-through-url-parameters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.