move data-flow

near · Mar 11, 2025 · b51fe6e · b51fe6e
1 parent 53f3a5b
commit b51fe6e
Show file tree

Hide file tree

Showing 6 changed files with 5 additions and 5 deletions.
diff --git a/docs/data-infrastructure/big-query.md b/docs/data-infrastructure/big-query.md
@@ -104,7 +104,7 @@ The tables available in the NEAR Public Lakehouse are:
 :::note References
 
 - [Protocol documentation](../protocol/basics.md)
-- [Near Data flow](../1.concepts/data-flow/near-data-flow.md)
+- [Near Data flow](../protocol/data-flow/near-data-flow.md)
 - [Lake Data structures](./lake-data-structures/toc.mdx)
 - [Protocol specification](https://nomicon.io/)
 

diff --git a/docs/data-infrastructure/lake-framework/building-indexers/nft-indexer.md b/docs/data-infrastructure/lake-framework/building-indexers/nft-indexer.md
@@ -171,7 +171,7 @@ async function handleStreamerMessage(
 
 ## Events and where to catch them
 
-First of all let's find out where we can catch the Events. We hope you are familiar with how the [Data Flow in NEAR Blockchain](/concepts/data-flow/near-data-flow), but let's revise our knowledge:
+First of all let's find out where we can catch the Events. We hope you are familiar with how the [Data Flow in NEAR Blockchain](/protocol/data-flow/near-data-flow), but let's revise our knowledge:
 - Mint an NFT is an action in an NFT contract (doesn't matter which one)
 - Actions are located in a [Receipt](/data-infrastructure/lake-data-structures/receipt)
 - A result of the Receipt execution is [ExecutionOutcome](/data-infrastructure/lake-data-structures/execution-outcome)

diff --git a/docs/data-infrastructure/lake-framework/building-indexers/python-nft-indexer.md b/docs/data-infrastructure/lake-framework/building-indexers/python-nft-indexer.md
@@ -120,7 +120,7 @@ async def handle_streamer_message(streamer_message: near_primitives.StreamerMess
 
 ## Events and where to catch them
 
-First of all let's find out where we can catch the Events. We hope you are familiar with how the [Data Flow in NEAR Blockchain](/concepts/data-flow/near-data-flow), but let's revise our knowledge:
+First of all let's find out where we can catch the Events. We hope you are familiar with how the [Data Flow in NEAR Blockchain](/protocol/data-flow/near-data-flow), but let's revise our knowledge:
 - Mint an NFT is an action in an NFT contract (doesn't matter which one)
 - Actions are located in a [Receipt](/data-infrastructure/lake-data-structures/receipt)
 - A result of the Receipt execution is [ExecutionOutcome](/data-infrastructure/lake-data-structures/execution-outcome)

diff --git a/docs/1.concepts/data-flow/near-data-flow.md → docs/protocol/data-flow/near-data-flow.md b/docs/1.concepts/data-flow/near-data-flow.md → docs/protocol/data-flow/near-data-flow.md
diff --git a/...concepts/data-flow/token-transfer-flow.md → ...protocol/data-flow/token-transfer-flow.md b/...concepts/data-flow/token-transfer-flow.md → ...protocol/data-flow/token-transfer-flow.md
diff --git a/website/sidebars.js b/website/sidebars.js
@@ -33,8 +33,8 @@ const sidebar = {
         },
         {
           "Data Flow": [
-            "concepts/data-flow/near-data-flow",
-            "concepts/data-flow/token-transfer-flow"
+            "protocol/data-flow/near-data-flow",
+            "protocol/data-flow/token-transfer-flow"
           ]
         },
         {