Add indexer guide

docs/concepts/data-collections.md

@@ -289,15 +289,15 @@ map.getSome(key)
 
 - To add data:
 
-```rs
+```rust
 pub fn add_lookup_map(&mut self, key: String, value: String) {
     self.lookup_map.insert(&key, &value);
 }
 ```
 
 - To get data:
 
-```rs
+```rust
 pub fn get_lookup_map(&self, key: String) -> String {
     match self.lookup_map.get(&key) {
         Some(value) => {
@@ -326,15 +326,15 @@ pub fn get_lookup_map(&self, key: String) -> String {
 
 - To add data:
 
-```rs
+```rust
 pub fn add_unordered_map(&mut self, key: String, value: String) {
     self.unordered_map.insert(&key, &value);
 }
 ```
 
 - To get data:
 
-```rs
+```rust
 pub fn get_unordered_map(&self, key: String) -> String {
     match self.unordered_map.get(&key) {
         Some(value) => {
@@ -365,15 +365,15 @@ pub fn get_unordered_map(&self, key: String) -> String {
 
 - To add data:
 
-```rs
+```rust
 pub fn add_tree_map(&mut self, key: String, value: String) {
     self.tree_map.insert(&key, &value);
 }
 ```
 
 - To get data:
 
-```rs
+```rust
 pub fn get_tree_map(&self, key: String) -> String {
     match self.tree_map.get(&key) {
         Some(value) => {

docs/concepts/indexer.md

@@ -0,0 +1,18 @@
+---
+id: indexer
+title: NEAR Indexer
+sidebar_label: Indexer
+---
+
+> NEAR Indexer is a library included with [nearcore](https://github.com/near/nearcore) that allows you to run a node on the network which listens for targeted information on the blockchain. The [NEAR Indexer Framework](https://github.com/near/nearcore/tree/master/chain/indexer) provides the logic of polling a node for blocks produced in a network then aggregating and streaming these blocks to a listener. 
+
+To better understand this, blockchain data is optimized for serialized writes, one block at a time, as the chain is being created. Querying the blockchain for data about a specific block or account is a fairly straightforward or "narrow" query. However, querying data across many blocks can be cumbersome because we have to aggregate results from multiple single-block queries. We can consider these "wide" queries.
+
+- An indexer listens to the stream of data as it's being written on chain and can then be immediately filtered and processed to detect interesting events or patterns.
+- This stream of data can then be written to a permanent database for later data analysis using a convenient query language like SQL.
+
+- One example that highlights the need for a "wide query" is when you use a seed phrase to recover one or more accounts. Since a seed phrase essentially represents a signing key pair, the recovery is for **all** accounts that share the associated public key. Therefore, when a seed phrase is used to recover an account via [NEAR Wallet](https://wallet.near.org/), the query requires that **all accounts** with a matching public key are found and recovered.
+
+- The easiest way to achieve a "wide query" is to utilize a database that has been filled by an indexing service. For this purpose we’ve built the [NEAR Indexer for wallet](https://github.com/near/near-indexer-for-wallet) which listens to all actions on chain that might create or delete [access keys](/docs/concepts/account#access-keys) and stores them into a relational database for easier querying of accounts.
+
+[ **[Click Here](/docs/tools/near-indexer)** ] For a walkthrough on creating an indexer.

docs/faq/faq.md

@@ -18,7 +18,7 @@ Each method call on a contract is recorded as a transaction. This transaction ca
 
 **Rust**
 
-```rs
+```rust
 env::signer_account_pk()
 ```
 
@@ -52,7 +52,7 @@ See here for an [example in our Guestbook](https://github.com/near-examples/gues
 See here for an [example in our Rust library test fixtures](https://github.com/near/near-sdk-rs/blob/master/examples/cross-contract-high-level/src/lib.rs#L125)
 
 
-```rs
+```rust
 ext_status_message::set_status(message, &account_id, 0, SINGLE_CALL_GAS);
 ```