> For the complete documentation index, see [llms.txt](https://tempdocs.zerog.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tempdocs.zerog.one/changelog/december-2024/discord-integration-new-pages-and-more.md).

# Discord Integration, new pages and more

TLDR; Added Discord integration on update of docs and some new pages.

## 💬Discord Integration

This will push changes to the documentation straight to our external update channel in Discord.

*Yes it's a small change, using this post we'll test it.*

## Documentation Streamlined

We've now separated all the building guides from the main documentation and changelogs. This allows for cleaner overall documentation, reducing chaos and improving readability. We've also made significant progress in adding our projects to the the "[project space](https://tempdocs.zerog.one/projects/)".

## New pages!

* Added different motherboards to the FAQ.
  * *Thanks, CharlotteBeLike.*
* Cleaned up broken links.
* Nebula BoM is almost done.
* Adding a basic structure to the project environment (menu) for build instructions.


---

# 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://tempdocs.zerog.one/changelog/december-2024/discord-integration-new-pages-and-more.md?ask=<question>&goal=<user_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.
