# NEWSLETTER

The NEARWEEK weekly newsletter provides an ecosystem  overview of what's happening within the NEAR Protocol & greater Open Web ecosystems.\
\
\
⚡️[Subscribe to the NEARWEEK RSS FEED](https://us1.campaign-archive.com/feed?u=ed13caf5cf7d37689d81ef60b\&id=86d4e11a12)\
\
📩 [Subscribe to the weekly NEARWEEK newsletter ](https://subscribe.nearweek.com/)

<figure><img src="/files/hmC0pOffSNbzeSHQURP0" alt=""><figcaption></figcaption></figure>

## NEARWEEK: TYPES OF CONTRIBUTION

Below is an outline of the different roles and opportunities available to those entering the NEARWEEK ecosystem

### **NEWS SUBMITTERS**

See any intersting news you want NEARWEEK to pick up? Everyone can help crowdsource news to the NEAR & Aurora Ecosystem by submitting links to us on Twitter via the [NEARWEEK BOT](https://docs.nearweek.com/start/newsletter/news-submission-via-twitter)

### **NEWS AGENTS & CURATORS**&#x20;

When you have mastered the art of submitting news, you can be eligible to become a news curator, this will get you voting power and you will receive an additional bonus every week from the newsletter. Read more regarding the [curation process](https://docs.nearweek.com/start/newsletter/news-curation-process).

### **NEARWEEK CORE TEAM**

Fancy joining the core team of NEARWEEK? If you impress us at NEARWEEK through dedication and consistent contribution as a news submitter & curator, we will reach out and offer additional working opportunities as they present themselves, don't be a stranger fren!

## SUBMISSION, CURATION & DISTRIBUTION&#x20;

In the following sections we will outline the each individual process of input, throughout and output of NEARWEEK news.&#x20;


---

# Agent Instructions: 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://docs.nearweek.com/start/content-overview/newsletter.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.