> For the complete documentation index, see [llms.txt](https://affine.gitbook.io/affine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://affine.gitbook.io/affine/affine-ambassadors/welcome.md).

# Welcome

AFFiNE Ambassadors are passionate, volunteer enthusiasts who teach and share AFFiNE with others. They do this through different ways - from leading communities, organizing events, creating content (from courses to social media posts), help with internalization, create and share templates and more.

AFFiNE Ambassadors:

* Are enthusiastic and passionate about teaching and sharing AFFiNE to the world
  * Community building - creating and managing groups, hosting events, engaging over social media
  * Content creation - creating and sharing templates, creating videos, building tools and apps, translating and helping with internationalization
* Decide what they do! The AFFiNE team is here to support you!
* Create their own content. Your content is yours and we hope we can help you promote it and share your content with a wider audience.
* Are volunteers. The program is completely voluntary, and members are free to leave at any time.
* Can generate income. If you want to monetize your content that's fine. Maybe through courses, consulting, or something else and we hope we can give you the support and resources you may need.


---

# 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:

```
GET https://affine.gitbook.io/affine/affine-ambassadors/welcome.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.