> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/xxx/faq.md). # Frequently Asked XQuestions All sorts of small topics are covered here ## Steps for contributing to this section 1. Git clone this repository to your computer: [campusrover/labnotebook](https://github.com/campusrover/labnotebook) 2. In the directory structure, find the folder called `faq`. In it you can create a `.md` file for your contribution. 3. Write your contribution using markdown. You can include images as well as links. There are many tutorials on Markdown but you most likely already know it. 4. If you want the title to be something other than the file name, then add: ``` --- title: Gooder Title author: Pito Salas description: nicer subtitle order: where does this one appear in order status: obsolete|new|tophit date: month-year --- ``` as the first few lines of the file 5. Git add, commit and push your changes. ## Note Brand new files (vs. edits) will not appear in the directory until it is rebuilt by so send them an email! --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://campus-rover.gitbook.io/lab-notebook/xxx/faq.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 `build a script that syncs our docs to a CMS` 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.