> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/lfx-drive/navigating-the-interface.md).
# Navigating the Interface
#### **1. Left Sidebar**
* **Drive**: Entry point to all your documents.
* **Project**: Shows the selected project whose documents you want to manage (e.g., *The Linux Foundation*).
* **Pinned**: Displays a list of project documents and folders that have been pinned by a project admin—or by you, if you have the necessary permissions. These pinned folders and document references are visible to all users across the project.
* **Support** Get help from our support team.
* **Profile**: Login, manage or logout of your profile.
#### 2. **Top Bar**
* **Search for a project**: Switch to a different project drive.
* **Search Documents**: Filter for documents that contain search string in their title.
#### 3. **Main Document Panel**
* Displays a list of:
* Folders indicated by folder icon in front of their name (e.g., `qa`, `Another Folder`)
* Document references inside the folders (e.g., `Test Document`, `jme test1234`)
* Tags applied to each file or folder
* Small number next to a folder indicates the number of document references within this folder. If there is no number next to the folder that means the folder is empty.
---
# 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.linuxfoundation.org/lfx/lfx-drive/navigating-the-interface.md?ask=&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.
