> For the complete documentation index, see [llms.txt](https://doc.anytype.io/anytype/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.anytype.io/anytype/documentation_cn/she-qu/join-the-open-source-project.md).
# “开源一切”倡议
## **如何做出贡献**
如果你是一名开发者，并希望为 Anytype 的生态系统做出贡献，请查看版本库内的 `关于贡献` 文档。
在 [Github](https://github.com/anyproto) 上关注我们，加入 [贡献者社区](https://github.com/orgs/anyproto/discussions)，共同建设 Anytype。
如果你想了解更多关于我们选择开放代码的原因，请查看下面的文章：
{% embed url="" %}
有关于许可证的任何问题，请访问 ，有关于技术的任何问题，请访问 。
---
# 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://doc.anytype.io/anytype/documentation_cn/she-qu/join-the-open-source-project.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.