More broken links

blog/2024-08-13.md

@@ -15,7 +15,7 @@ As the NEAR ecosystem continues to decentralize, Pagoda will cease operations wi
 The critical services below will continue to be operated and maintained by Pagoda until they are smoothly transitioned to new operators in the NEAR ecosystem during the second half of 2024:
 
 -   [near.org RPC](https://docs.near.org/api/rpc/providers) ([Request for Proposals](https://dev.near.org/infrastructure-committee.near/widget/app?page=rfp&id=2))
--   [NEAR Lake](https://docs.near.org/concepts/advanced/near-lake-framework) ([Request for Proposals](https://dev.near.org/infrastructure-committee.near/widget/app?page=rfp&id=3))
+-   [NEAR Lake](https://docs.near.org/build/data-infrastructure/lake-framework/near-lake-framework) ([Request for Proposals](https://dev.near.org/infrastructure-committee.near/widget/app?page=rfp&id=3))
 -   [BigQuery Public Dataset](https://docs.near.org/build/data-infrastructure/big-query) ([Request for Proposals](https://dev.near.org/infrastructure-committee.near/widget/app?page=rfp&id=4))
 -   [Node Snapshots](https://near-nodes.io/intro/node-data-snapshots) 
 -   [State Sync](https://near-nodes.io/rpc/state-sync)

docs/2.build/6.data-infrastructure/lake-framework/building-indexers/nft-indexer.md

@@ -31,7 +31,7 @@ In this tutorial our goal is to show you how you can "listen" to the Events cont
 
 As the example we will be building an indexer that watches all the NFTs minted following the [NEP-171 Events](https://nomicon.io/Standards/Tokens/NonFungibleToken/Event) standard, assuming we're collectors who don't want to miss a thing. Our indexer should notice every single NFT minted and give us a basic set of data like: in what Receipt it was minted, and show us the link to a marketplace (we'll cover [Paras](https://paras.id) and [Mintbase](https://mintbase.io) in our example).
 
-We will use JS version of [NEAR Lake Framework](/concepts/advanced/near-lake-framework) in this tutorial. Though the concept is the same for Rust, but we want to show more people that it's not that complex to build your own indexer.
+We will use JS version of [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) in this tutorial. Though the concept is the same for Rust, but we want to show more people that it's not that complex to build your own indexer.
 
 ## Preparation
 

docs/2.build/6.data-infrastructure/lake-framework/building-indexers/python-nft-indexer.md

@@ -13,7 +13,7 @@ sidebar_label: "NFT indexer for Python"
 
 ## The Goal
 
-This tutorial ends with a working NFT indexer built on top [NEAR Lake Framework for Python](/concepts/advanced/near-lake-framework). The indexer is watching for `nft_mint` [Events](https://nomicon.io/Standards/EventsFormat) and prints some relevant data:
+This tutorial ends with a working NFT indexer built on top [NEAR Lake Framework for Python](/build/data-infrastructure/lake-framework/near-lake-framework/). The indexer is watching for `nft_mint` [Events](https://nomicon.io/Standards/EventsFormat) and prints some relevant data:
 - `receipt_id` of the [Receipt](/build/data-infrastructure/lake-data-structures/receipt) where the mint has happened
 - Marketplace
 - NFT owner account name
@@ -31,7 +31,7 @@ In this tutorial our goal is to show you how you can "listen" to the Events cont
 
 As the example we will be building an indexer that watches all the NFTs minted following the [NEP-171 Events](https://nomicon.io/Standards/Tokens/NonFungibleToken/Event) standard, assuming we're collectors who don't want to miss a thing. Our indexer should notice every single NFT minted and give us a basic set of data like: in what Receipt it was minted, and show us the link to a marketplace (we'll cover [Paras](https://paras.id) and [Mintbase](https://mintbase.io) in our example).
 
-We will use Python version of [NEAR Lake Framework](/concepts/advanced/near-lake-framework) in this tutorial. Though the concept is the same for Rust, but we want to show more people that it's not that complex to build your own indexer.
+We will use Python version of [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) in this tutorial. Though the concept is the same for Rust, but we want to show more people that it's not that complex to build your own indexer.
 
 ## Preparation
 

docs/2.build/6.data-infrastructure/lake-framework/migrating-to-near-lake-framework.md

@@ -5,7 +5,7 @@ sidebar_label: Migrating to NEAR Lake framework
 # Migrating to NEAR Lake Framework
 
 
-We encourage everyone who don't have a hard requirement to use [NEAR Indexer Framework](/concepts/advanced/near-indexer-framework) consider the migration to [NEAR Lake Framework](/concepts/advanced/near-lake-framework).
+We encourage everyone who don't have a hard requirement to use [NEAR Indexer Framework](/concepts/advanced/near-indexer-framework) consider the migration to [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework).
 
 In this tutorial we'll show you how to migrate the project using [indexer-tx-watcher-example](https://github.com/near-examples/indexer-tx-watcher-example) as a showcase.
 
@@ -83,7 +83,7 @@ near-lake-framework = "0.4.0"
 
 ## Change the clap configs
 
-Currently we have structure `Opts` that has a subcommand with `Run` and `Init` command. Since [NEAR Lake Framework](/concepts/advanced/near-lake-framework) doesn't need `data` and config files we don't need `Init` at all. So we need to combine some structures into `Opts` itself.
+Currently we have structure `Opts` that has a subcommand with `Run` and `Init` command. Since [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) doesn't need `data` and config files we don't need `Init` at all. So we need to combine some structures into `Opts` itself.
 
 ```rust title=src/config.rs
 ...
@@ -271,7 +271,7 @@ async fn main() -> Result<(), tokio::io::Error> {
 
 ```
 
-Let's cast `LakeConfig` from `Opts` and instantiate [NEAR Lake Framework](/concepts/advanced/near-lake-framework)'s `stream`
+Let's cast `LakeConfig` from `Opts` and instantiate [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework)'s `stream`
 
 ```rust title=src/main.rs
 #[tokio::main]
@@ -341,7 +341,7 @@ We're done. That's pretty much entire `main()` function. Drop the old one if you
 
 ## Changes in other function related to data types
 
-Along with [NEAR Lake Framework](/concepts/advanced/near-lake-framework) release we have extracted the structures created for indexers into a separate crate. This was done in order to avoid dependency on `nearcore` as now you can depend on a separate crate that is already [published on crates.io](https://crates.io/crates/near-indexer-primitives) or on NEAR Lake Framework that exposes that crate.
+Along with [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) release we have extracted the structures created for indexers into a separate crate. This was done in order to avoid dependency on `nearcore` as now you can depend on a separate crate that is already [published on crates.io](https://crates.io/crates/near-indexer-primitives) or on NEAR Lake Framework that exposes that crate.
 
 ### `listen_blocks`
 
@@ -394,7 +394,7 @@ fn is_tx_receiver_watched(
 
 ## Conclusion
 
-And now we have a completely migrated to [NEAR Lake Framework](/concepts/advanced/near-lake-framework) indexer.
+And now we have a completely migrated to [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) indexer.
 
 We are posting the complete diffs for the reference
 

docs/2.build/6.data-infrastructure/lake-framework/near-lake-state-changes-indexer.md

@@ -11,13 +11,13 @@ title: NEAR Lake Indexer Tutorial
 
 :::info Version 0.2.0
 
-The video is based on the [`near-lake-framework`](/concepts/advanced/near-lake-framework) version 0.2.0
+The video is based on the [`near-lake-framework`](/build/data-infrastructure/lake-framework/near-lake-framework) version 0.2.0
 
 At the same time we're keeping the source code up to date with the latest version of the published crate.
 
 :::
 
-We've created a video tutorial to empower the release announcement of [NEAR Lake Framework](/concepts/advanced/near-lake-framework).
+We've created a video tutorial to empower the release announcement of [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework).
 
 In this tutorial you will build an indexer application to watch for any `StateChange`s affecting the account or a list of account provided.
 

docs/2.build/6.data-infrastructure/lake-framework/near-lake.md

@@ -50,7 +50,7 @@ The data structure used by Lake Indexer is the following:
 
 ### How to use it
 
-We have created the [NEAR Lake Framework](/concepts/advanced/near-lake-framework) to have a simple straightforward way to create an indexer on top of the data stored by NEAR Lake itself.
+We have created the [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) to have a simple straightforward way to create an indexer on top of the data stored by NEAR Lake itself.
 
 :::info NEAR Lake Framework
 

docs/2.build/6.data-infrastructure/lake-framework/running-near-lake/lake-start-options.md

@@ -7,7 +7,7 @@ sidebar_label: "Start options"
 
 ## The End
 
-This tutorial ends with the example code of the simple indexer built on top of [NEAR Lake Framework](/concepts/advanced/near-lake-framework) that can start:
+This tutorial ends with the example code of the simple indexer built on top of [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) that can start:
 - from specified block height (out of the box)
   ```bash
   ./target/release/indexer mainnet from-block 65359506
@@ -34,11 +34,11 @@ There is another important side - the maintenance. This involves:
 
 Almost in all of the above cases you might want to start or restart your indexer not only from the specific block you need to provide, but from the block it was stopped, or from the latest final block in the network.
 
-[NEAR Lake Framework](/concepts/advanced/near-lake-framework) doesn't provide such options. Actually, we didn't empower the library with these options to start indexer intentionally.
+[NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) doesn't provide such options. Actually, we didn't empower the library with these options to start indexer intentionally.
 
 :::info Intent
 
-We want to keep [NEAR Lake Framework](/concepts/advanced/near-lake-framework) crate in the narrowest possible way. The goal for the library is to do a single job and allow it to be empowered with any features but outside of the crate itself
+We want to keep [NEAR Lake Framework](/build/data-infrastructure/lake-framework/near-lake-framework) crate in the narrowest possible way. The goal for the library is to do a single job and allow it to be empowered with any features but outside of the crate itself
 
 :::
 

docs/3.tutorials/nfts/1-skeleton.md

@@ -65,7 +65,7 @@ Here is a brief description of what each source file is responsible for:
 | [mint.rs](#mintrs)               | Contains token minting logic                                                    |
 | [nft_core.rs](#nft_corers)       | Core logic that allows you to transfer NFTs between users.                      |
 | [royalty.rs](#royaltyrs)         | Contains payout-related functions                                               |
-| [events.rs](#events)             | Contains events related structures                                              |
+| [events.rs](#eventsrs)             | Contains events related structures                                              |
 
 :::tip
 Explore the code in our [GitHub repository](https://github.com/near-examples/nft-tutorial/).

docs/3.tutorials/nfts/2-minting.md

@@ -420,7 +420,7 @@ In this tutorial, you went through the basics of setting up and understand the l
 
 You first looked at [what it means](#what-does-minting-mean) to mint NFTs and how to break down the problem into more feasible chunks. You then started modifying the skeleton contract chunk by chunk starting with solving the problem of [storing information / state](#storing-information) on the contract. You then looked at what to put in the [metadata and token information](#metadata-and-token-info). Finally, you looked at the logic necessary for [minting NFTs](#minting-logic).
 
-After the contract was written, it was time to deploy to the blockchain. You [deployed the contract](#deploy-the-contract) and [initialized it](#initialize-contract). Finally, you [minted your very first NFT](#minting-our-first-nft) and saw that some changes are needed before you can view it in the wallet.
+After the contract was written, it was time to deploy to the blockchain. You [deployed and initialized the contract](#deploy-the-contract). Finally, you [minted your very first NFT](#minting-our-first-nft) and saw that some changes are needed before you can view it in the wallet.
 
 ---
 

docs/6.integrations/create-transactions.md

@@ -394,7 +394,7 @@ const signedTransaction = new nearAPI.transactions.SignedTransaction({
 Final step is to encode and send the transaction.
 
 - First we serialize transaction into [Borsh](https://borsh.io/), and store the result as `signedSerializedTx`. _(required for all transactions)_
-- Then we send the transaction via [RPC call](/api/rpc/introduction) using the `sendJsonRpc()` method nested inside [`near`](#setting-up-connection-to-near).
+- Then we send the transaction via [RPC call](/api/rpc/introduction) using the `sendJsonRpc()` method nested inside [`near`](#setting-up-connection-to-near-1).
 
 ```js
 // encodes transaction to serialized Borsh (required for all transactions)

docs/welcome.md

@@ -70,7 +70,7 @@ Imagine a place where you can build Web3 apps with the simplicity of Web2. Imagi
             "What is Data Infrastructure?": "/build/data-infrastructure/what-is",
             "BigQuery": "/build/data-infrastructure/big-query",
             "Data APIs": "/build/data-infrastructure/data-apis",
-            "Lake Framework": "/concepts/advanced/near-lake-framework",
+            "Lake Framework": "/build/data-infrastructure/lake-framework/near-lake-framework",
           }}
     />
 </Container>