> 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/fiiva/contribution-guide.md).

# contribution-guide.md

*Author: Pito Salas, Date: April 2023*

When contributing, please make sure to do the following:

1. Proofread your writing for spelling and grammatical errors, especially in areas where excat typing is important (e.g. code snippets)
2. Place your files in the appropriate folders. Only create new folders if absolutely necessary. If you make a new folder, give it a README which clearly describes the content of the folder
3. Add your file to Summary.md so it is accessible from the gitbook webpage
4. Give your images common sense names. They should be descriptive and/ or associative. "p1.png" is bad, "gazebo\_img1.png" is better.
5. Only use hyphens, not underscores, in filenames.
6. Try to order files in SUMMARY.md is a way that makes sense if they were to be read through sequentially
7. Follow Markdown format guidleines. There is a Markdown extenstion for VS code which will assist you in this endeavor. Here are some common mistakes:
   1. No trailing spaces at the end of lines
   2. One (and only one) blank new line on either side of Headers, lists, and code blocks
   3. Use consistant spacing
   4. no embedded HTML or raw links
   5. no trailing punctuation in headers
   6. Do not skip header levels, only one H1
8. Furthermore, please follow these style guidelines:
   1. Do not use bold or italics in headers
   2. Do not use emphasis to take the place of a code snippet
   3. Label your code snippets (starting with \`\`\`)with the language they contain! common languages in this course are `python`, `bash`, `xml` and `c++`
   4. Surround package names, file paths and other important info of this nature with single backticks (\`)
   5. Add a byline at the bottom of the page, including your name and date of publishing


---

# 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://campus-rover.gitbook.io/lab-notebook/fiiva/contribution-guide.md?ask=<question>&goal=<endgoal>
```

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