fix links

Author: rtso

apps/nextra/next.config.mjs

@@ -397,6 +397,11 @@ export default withBundleAnalyzer(
         destination: "/en/build/indexer/indexer-sdk/quickstart",
         permanent: true,
       },
+      {
+        source: "/indexer/indexer-sdk/documentation",
+        destination: "/en/build/indexer/indexer-sdk/documentation",
+        permanent: true,
+      },
       {
         source: "/indexer/indexer-sdk/documentation/setup",
         destination: "/en/build/indexer/indexer-sdk/documentation/setup",

apps/nextra/pages/en/build/cli/running-a-local-network.mdx

@@ -118,7 +118,7 @@ As you can see from the example output in step 4, once the local network is runn
 
 - [Node API](../../network/nodes/aptos-api-spec.mdx): This is a REST API that runs directly on the node. It enables core write functionality such as transaction submission and a limited set of read functionality, such as reading account resources or Move module information.
 - [Indexer API](../indexer/aptos-hosted.mdx): This is a [GraphQL](https://graphql.org/) API that provides rich read access to indexed blockchain data. If you click on the URL for the Indexer API above, by default [http://127.0.0.1:8090](http://127.0.0.1:8090/), it will open the Hasura Console, a web UI that will help you query the Indexer GraphQL API.
-- [Transaction Stream Service](../indexer/txn-stream.mdx): This is a gRPC stream of transactions used by the Indexer API and SDK. This is only relevant to you if you are developing a custom processor with the [Indexer SDK](../indexer/indexer-sdk.mdx).
+- [Transaction Stream Service](../indexer/txn-stream.mdx): This is a gRPC stream of transactions used by the Indexer API and SDK. This is only relevant to you if you are developing a [Indexer SDK](../indexer/indexer-sdk.mdx) custom processor.
 - [Postgres](https://www.postgresql.org/): This is the database that the Indexer processors write to. The Indexer API reads from this database.
 - [Faucet](../apis/faucet-api.mdx): You can use this to fund accounts on your local network.
 
@@ -166,7 +166,7 @@ const client = new Aptos(config);
 Sometimes while developing it is helpful to reset the local network back to its initial state, for example:
 
 - You made backwards incompatible changes to a Move module, and you'd like to redeploy it without renaming it or using a new account.
-- You are building a custom indexer processor with the [Indexer SDK](./indexer/indexer-sdk.mdx) and would like to index using a fresh network.
+- You are building an [Indexer SDK](./indexer/indexer-sdk.mdx) custom processor and would like to index using a fresh network.
 - You want to clear all on chain state, e.g. accounts, objects, etc.
 
 To start with a brand new local network, use the `--force-restart` flag:

apps/nextra/pages/en/build/indexer/architecture.mdx

@@ -29,9 +29,9 @@ Here is how the Indexer creates that API at a high-level:
   />
 </center>
 
-The Indexer uses the [Transaction Stream Service](./txn-stream.mdx) and [Custom Processors](./custom-processors.mdx) to update a database with rich tables. Then it exposes an API for Aptos apps to access the consolidated data.
+The Indexer uses the [Transaction Stream Service](./txn-stream.mdx) and custom processors written with the [Indexer SDK](./indexer-sdk.mdx) to update a database with rich tables. Then it exposes an API for Aptos apps to access the consolidated data.
 
-For situations where you need to go beyond the Aptos hosted Indexer API data, you will want to create a [custom processor](./custom-processors.mdx).
+For situations where you need to go beyond the Aptos hosted Indexer API data, you will want to create a custom processor with the Indexer SDK (./indexer-sdk.mdx).
 
 Writing a custom processor can help you:
 1. Get access to different types of data.

apps/nextra/pages/en/build/indexer/indexer-sdk.mdx

@@ -26,27 +26,6 @@ Learn how to use the Indexer SDK through guides and documentation.
   </Card>
 </Cards>
 
-## Architecture of the Indexer SDK
-
-In the Aptos indexing stack, a processor indexes a specific subset of data from the blockchain and ingests the data into an external database.
-
-Each processor follows this general flow:
-
-1. Receive a stream of Aptos transactions
-2. Extract the relevant data from the transactions
-3. Transform and merge the extracted data into a coherent, standardized schema
-4. Store the transformed data into a database
-
-The Aptos Indexer SDK allows you to write and model each of your processor as a graph of independent `Step`'s'.
-Each `Step` has an input and an output, and the output of one `Step` is connected to the input of another `Step` by a channel.
-The flow above can be modeled as a graph of `Step`'s connected by channels.
-
-The Indexer SDK's architecture simplifies writing custom processors in several ways:
-
-1. You can reuse `Step` implementations across processors which reduces duplication of common data extraction logic. 
-2. The SDK collects basic performance metrics, like the number of transactions processed, for each `Step`, which enables observability into subcomponents of the processor. 
-3. Since each `Step` is independent, you can safely customize parts of the processor without breaking the other pieces. 
-For example, you can add additional `Step`'s to pre/post-process data or batch data writes. Each `Step` can also be tested in isolation from the rest of the processor. 
 
 ## Example Processors 
 As a reference, you can see all Aptos-Hosted processors that comprise the Indexer API [here](https://github.com/aptos-labs/aptos-indexer-processors). 

apps/nextra/pages/en/build/indexer/indexer-sdk/documentation.mdx

@@ -0,0 +1,29 @@
+---
+title: "Documentation"
+---
+import { Callout } from 'nextra/components'
+import { IndexerBetaNotice } from '@components/index';
+
+# Documentation
+
+## Architecture of the Indexer SDK
+
+In the Aptos indexing stack, a processor indexes a specific subset of data from the blockchain and ingests the data into an external database.
+
+Each processor follows this general flow:
+
+1. Receive a stream of Aptos transactions
+2. Extract the relevant data from the transactions
+3. Transform and merge the extracted data into a coherent, standardized schema
+4. Store the transformed data into a database
+
+The Aptos Indexer SDK allows you to write and model each of your processor as a graph of independent `Step`'s'.
+Each `Step` has an input and an output, and the output of one `Step` is connected to the input of another `Step` by a channel.
+The flow above can be modeled as a graph of `Step`'s connected by channels.
+
+The Indexer SDK's architecture simplifies writing custom processors in several ways:
+
+1. You can reuse `Step` implementations across processors which reduces duplication of common data extraction logic. 
+2. The SDK collects basic performance metrics, like the number of transactions processed, for each `Step`, which enables observability into subcomponents of the processor. 
+3. Since each `Step` is independent, you can safely customize parts of the processor without breaking the other pieces. 
+For example, you can add additional `Step`'s to pre/post-process data or batch data writes. Each `Step` can also be tested in isolation from the rest of the processor. 

apps/nextra/pages/en/build/indexer/indexer-sdk/documentation/parsing-txns.mdx

@@ -17,7 +17,7 @@ Fundamentally an indexer processor is just something that consumes a stream of a
 
 ## What is a transaction?
 
-A transaction is a unit of execution on the Aptos blockchain. If the execution of the program in a transaction (e.g. starting with an entry function in a Move module) is successful, the resulting change in state will be applied to the ledger. Learn more about the transaction lifecycle at [this page](../../../network/blockchain/blockchain-deep-dive.mdx#life-of-a-transaction).
+A transaction is a unit of execution on the Aptos blockchain. If the execution of the program in a transaction (e.g. starting with an entry function in a Move module) is successful, the resulting change in state will be applied to the ledger. Learn more about the transaction lifecycle at [this page](../../../../network/blockchain/blockchain-deep-dive.mdx#life-of-a-transaction).
 
 There are four types of transactions on Aptos:
 
@@ -28,7 +28,7 @@ There are four types of transactions on Aptos:
 
 The first 3 of these are internal to the system and are not relevant to most processors; we do not cover them in this guide.
 
-Generally speaking, most user transactions originate from a user calling an entry function in a Move module deployed on chain, for example `0x1::coin::transfer`. In all other cases they originate from [Move scripts](../../smart-contracts/scripts.mdx). You can learn more about the different types of transactions [here](../../../network/blockchain/txns-states.mdx#types-of-transaction-payloads).
+Generally speaking, most user transactions originate from a user calling an entry function in a Move module deployed on chain, for example `0x1::coin::transfer`. In all other cases they originate from [Move scripts](../../../../smart-contracts/scripts.mdx). You can learn more about the different types of transactions [here](../../../../network/blockchain/txns-states.mdx#types-of-transaction-payloads).
 
 A user transaction that a processor handles contains a variety of information. At a high level it contains:
 
@@ -47,7 +47,7 @@ The payload is what the user submits to the blockchain when they wish to execute
 - The address + module name + function name of the function being executed.
 - The arguments to the function.
 
-There is other potentially interesting information in the payload that you can learn about at [this page](../../../network/blockchain/txns-states.mdx#contents-of-a-transaction).
+There is other potentially interesting information in the payload that you can learn about at [this page](../../../../network/blockchain/txns-states.mdx#contents-of-a-transaction).
 
 ### Events
 

apps/nextra/pages/en/build/indexer/txn-stream/aptos-hosted-txn-stream.mdx

@@ -8,7 +8,7 @@ import { IndexerBetaNotice } from '@components/index';
 
 <IndexerBetaNotice />
 
-If you are running your own instance of the [Indexer API](../../indexer.mdx), or a [custom processor](../custom-processors.mdx), you must have access to an instance of the Transaction Stream Service. This page contains information about how to use the Aptos Labs Hosted Transaction Stream Service.
+If you are running your own instance of the [Indexer API](../../indexer.mdx), or an [Indexer SDK](../indexer-sdk.mdx) custom processor, you must have access to an instance of the Transaction Stream Service. This page contains information about how to use the Aptos Labs Hosted Transaction Stream Service.
 
 ## Endpoints
 

apps/nextra/pages/en/network/nodes/localnet/local-development-network.mdx

@@ -118,7 +118,7 @@ As you can see from the example output in step 4, once the local network is runn
 {/* TODO: replace API spec link */}
 - [Node API](../aptos-api-spec.mdx): This is a REST API that runs directly on the node. It enables core write functionality such as transaction submission and a limited set of read functionality, such as reading account resources or Move module information.
 - [Indexer API](../../../build/indexer/aptos-hosted.mdx): This is a [GraphQL](https://graphql.org/) API that provides rich read access to indexed blockchain data. If you click on the URL for the Indexer API above, by default [http://127.0.0.1:8090](http://127.0.0.1:8090/), it will open the Hasura Console, a web UI that will help you query the Indexer GraphQL API.
-- [Transaction Stream Service](../../../build/indexer/txn-stream.mdx): This is a gRPC stream of transactions used by the Indexer API. This is only relevant to you if you are developing a custom processor with the [Indexer SDK](../../../build/indexer/indexer-sdk.mdx).
+- [Transaction Stream Service](../../../build/indexer/txn-stream.mdx): This is a gRPC stream of transactions used by the Indexer API. This is only relevant to you if you are developing an[Indexer SDK](../../../build/indexer/indexer-sdk.mdx) custom processor.
 - [Postgres](https://www.postgresql.org/): This is the database that the Indexer processors write to. The Indexer API reads from this database.
 - [Faucet](../../../build/apis/faucet-api.mdx): You can use this to fund accounts on your local network.