> For the complete documentation index, see [llms.txt](https://docs.nearbuilders.com/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nearbuilders.com/resources/developer-onboarding/dev-resources.md).

# Dev Resources

[**nomicon.io** ](https://nomicon.io/)

Low level protocol documentation. If you are a blockchain engineer interested in contributing to the core protocol, this is your source of truth (e.g. nomicon explains how NEAR implements Merkle Proofs). Also enumerates NEPs and their specifications. I think Pagoda's protocol team has ownership of this.

[**docs.near.org**](https://docs.near.org/)

Developer documentation. If you are a web2 or web3 dev interested in learning what NEAR is, and how to implement a dApp, this is your page

Doesn't mention NEPs, but how to implement it (e.g. FT, NFT, and how to make a marketplace). 

Pagoda's DevRel is DRI

<br>

[**wiki.near.org**](https://wiki.near.org/)

{% embed url="<https://wiki.near.org>" %}

Information about everything the protocol has to offer including usage, infrastructure, opportunities, and guilds".&#x20;

Near Foundation is DRI, make a PR to this knowledge base here <https://github.com/near/wiki>

[**https://github.com/near**](https://github.com/near)&#x20;

{% embed url="<https://github.com/near>" %}

Official NEAR Github home of near-core, NEPs, NEAR RS SDK, NEAR JS SDK, wiki, and so much more.&#x20;

<https://near.social/#/mob.near/widget/MyPage?accountId=hack.near>

{% embed url="<https://near.social/#/mob.near/widget/MyPage?accountId=hack.near>" %}

[**https://near.academy/**](https://near.academy/)

Interactive NEAR Development course

<https://nearprimer.com/>

{% embed url="<https://nearprimer.com/>" %}

Gamified learning materials on NEAR


---

# 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://docs.nearbuilders.com/resources/developer-onboarding/dev-resources.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.