feat(docs): removing indexer from docs (#1128)

Co-authored-by: Joshua Croft <joshuacroft@Joshuas-MacBook-Pro.local>
Co-authored-by: felix.bucsa <72919584+FelixNicolaeBucsa@users.noreply.github.com>

next.config.js

@@ -636,6 +636,26 @@ module.exports = withNextra({
         destination: "/examples/examplestech/jupyter-agent",
         permanent: true,
       },
+      {
+        source: "/concepts/fetch-network/indexer",
+        destination: "/concepts/fetch-network/intro-fetch-network",
+        permanent: true,
+      },
+      {
+        source: "/concepts/fetch-network/indexer/:path*",
+        destination: "/concepts/fetch-network/intro-fetch-network",
+        permanent: true,
+      },
+      {
+        source: "/references/indexer",
+        destination: "/concepts/fetch-network/intro-fetch-network",
+        permanent: true,
+      },
+      {
+        source: "/references/indexer/:path*",
+        destination: "/concepts/fetch-network/intro-fetch-network",
+        permanent: true,
+      },
     ];
   },
 });

pages/concepts.mdx

@@ -98,16 +98,6 @@ import { AgentsIcon, AgentverseIcon ,FetchNetwork, LedgerIcon} from "src/icons/m
         path: "/concepts/fetch-network/ledger/validators",
       },
     ],
-  },
-  {
-    type: "Indexer",
-    icon: AgentsIcon,
-    data: [
-      {
-        title: "Indexer: An Introduction",
-        path: "/concepts/fetch-network/indexer",
-      },
-    ],
   }
 ]} />
 

pages/concepts/fetch-network/_meta.json

@@ -8,6 +8,5 @@
     "timestamp": true
   },
   "almanac": { "title": "The Almanac contract", "timestamp": true },
-  "ledger": { "title": "Ledger", "timestamp": true },
-  "indexer": { "title": "Indexer", "timestamp": true }
+  "ledger": { "title": "Ledger", "timestamp": true }
 }

pages/concepts/fetch-network/intro-fetch-network.mdx

@@ -14,12 +14,10 @@ The Almanac facilitates remote communication between agents but also provides a
 
 The [Fetch Name Service (FNS) ↗️](/guides/agents/advanced/name-service) is another key element providing human-readable names for interacting with Agents and Functions. The FNS simplifies resource identification and makes it easier for developers and users to access agents and functions and thus enhancing overall user accessibility.
 
-### Fetch Ledger and Indexer
+### Fetch Ledger
 
 The [Fetch Ledger ↗️](/concepts/fetch-network/ledger/intro) is an additional central component of the Fetch Network. It provides a secure, decentralized, and transparent record of all transactions and data exchanges that take place within the Fetch Ecosystem itself. The Ledger uses the [FET token ↗️](/concepts/fetch-network/native-and-erc20-fet-tokens) to facilitate transactions, agent interactions, and smart contracts execution, but it also to ensure that the integrity and efficiency of the Network is maintained.
 
-In order to enhance the Ledger data accessibility, the Fetch Network employs an [Indexer ↗️](/concepts/fetch-network/indexer) which is based on **SubQuery**. The aim of the Indexer is to organize and index the Ledger data and provide a GraphQL API to enable developers to efficiently query and retrieve information for their applications directly from the Fetch Ledger.
-
 ### Jenesis
 
 An additional tool is [Jenesis ↗️](/guides/fetch-network/jenesis/getting-started); it simplifies the development and deployment of smart contracts and decentralized applications (i.e., dApps) on the Fetch Network and other CosmWasm-enabled platforms. Jenesis offers a streamlined environment for developers that reduces the complexity of building blockchain-based solutions and accelerates the deployment of decentralized services and applications.
@@ -30,6 +28,6 @@ As a complementary tool to the above ones, [CosmPy ↗️](/guides/fetch-network
 
 ### Conclusions
 
-These components together constitute the backbone structure of the Fetch Network. These tools are essential in enabling a decentralized economy of autonomous Agents and AI-driven Agent Functions. By leveraging the Fetch Ledger, Almanac Contract, FNS, Indexer, Jenesis, and CosmPy, the Fetch Network focuses on creating an environment where agents can autonomously manage tasks, interact with each other, and create value in a secure and scalable way.
+These components together constitute the backbone structure of the Fetch Network. These tools are essential in enabling a decentralized economy of autonomous Agents and AI-driven Agent Functions. By leveraging the Fetch Ledger, Almanac Contract, FNS, Jenesis, and CosmPy, the Fetch Network focuses on creating an environment where agents can autonomously manage tasks, interact with each other, and create value in a secure and scalable way.
 
 The FET token empowers the Fetch Ecosystem, providing the economic incentive and governance framework necessary for the sustainability and evolution of the Network itself. The token acts both as the medium of exchange and the incentive structure for participants, while supporting the Network's governance and staking mechanisms.

pages/examples.mdx

@@ -128,10 +128,6 @@ import { AgentsIcon, LedgerIcon, AgentverseIcon} from "src/icons/main-page-icons
         title: "Agentverse Functions: register a coin toss function on DeltaV",
         path: "/examples/intermediate/coin-toss"
       },
-      {
-        title: "Agentverse Functions: register a dice roll function on DeltaV",
-        path: "/examples/intermediate/dice-roll"
-      },
       {
         title: "Agentverse Functions: register a local agent as a function",
         path: "/examples/local-agent-registration"
@@ -146,7 +142,7 @@ import { AgentsIcon, LedgerIcon, AgentverseIcon} from "src/icons/main-page-icons
       },
       {
         title: "Locally Hosted Agent with LangChain Integration",
-        path: "/examples/intermediate/local-agent-langchain"
+        path: "/examples/examplestech/local-agent-langchain"
       }
     ]
   },

pages/examples/agentverse/running-an-agent-on-agentverse.mdx

@@ -178,7 +178,7 @@ Let's consider the following local agent example:
 
 You can create a Mailbox by retrieving your **local agent address** and head over to the **Agentverse: My Agents** tab. Click on **Local Agents** and click on **Connect Local Agent** button. Provide the address and name of the local agent you wish to retrieve and wait for confirmation. You will then be able to see a **Mailbox API Key**. Copy and paste it within your local agent code by filling up the `AGENT_MAILBOX_KEY` field inline and restart the agent.
 
-For an example of a complete code for a local agent with protocols registered on the Agentverse using the Mailbox feature, checkout this [example ↗️](/examples/intermediate/local-agent-langchain).
+For an example of a complete code for a local agent with protocols registered on the Agentverse using the Mailbox feature, checkout this [example ↗️](/examples/examplestech/local-agent-langchain).
 
 When running the above local agent, you will see something like this on your terminal:
 

pages/guides/agent-courses/agents-for-ai.mdx

@@ -240,7 +240,7 @@ There are a lot of really cool, neat things you need to know from code above. Le
 
     - `OPENAI_API_KEY` is our API key to OpenAI's APIs.
 
-We can now initialize the Agent and define the [Protocol ↗️](/references/uagents/uagents-protocols/agent-protocols). To read more about **Agent objects**, please check out [the reference docs ↗️](/references/uagents/uagents-api/agent#agent-objects).
+We can now initialize the Agent and define the [Protocol ↗️](/references/uagents/uagents-protocols/agent-protocols). To read more about **Agent objects**, please check out [the reference docs ↗️](/references/uagents/api/agent#agent-objects).
 
 Then, we have the `on_message()` [handler ↗️](/guides/agents/intermediate/handlers):
 

pages/guides/quickstart-with/CrewAI/creating-an-agent-with-crewai.mdx

@@ -186,7 +186,7 @@ Agents are defined with the `Agent` class:
 
 A `seed` is a unique phrase which `uagents` library uses to create a unique private key pair for your agent. If you change your `seed` you may lose access to previous messages, and also, the agent's address registered to the Almanac will change subsequently. The `port` allows us to define a local port for messages to be received. The `endpoint` defines the path to the in-built Rest API. The `name` defines the name of the agent.
 
-There are more options for the `Agent` class; see [`Agent` Class ↗️](/references/uagents/uagents-api/agent) for further reference.
+There are more options for the `Agent` class; see [`Agent` Class ↗️](/references/uagents/api/agent) for further reference.
 
 We then need to define our **communication model**:
 

pages/guides/quickstart-with/langchain/creating-an-agent-with-langchain.mdx

@@ -136,7 +136,7 @@ Agents are defined with the `Agent` class:
 
 A `seed` is a unique phrase which `uagents` library uses to create a unique private key pair for your agent. If you change your `seed` you may lose access to previous messages, and also, the agent's address registered to the Almanac will change subsequently. The `port` allows us to define a local port for messages to be received. The `endpoint` defines the path to the in-built Rest API. The `name` defines the name of the agent.
 
-There are more options for the `Agent` class; see [`Agent` Class ↗️](/references/uagents/uagents-api/agent) for further reference.
+There are more options for the `Agent` class; see [`Agent` Class ↗️](/references/uagents/api/agent) for further reference.
 
 We then need to define our communication model:
 

pages/references.mdx

@@ -108,32 +108,6 @@ import { AgentsIcon, LedgerIcon , AsiIcon} from "src/icons/main-page-icons"
         path: "/references/cosmpy/wallet-generation",
       }
     ]
-  },
-  {
-    type: "Indexer",
-    icon: AgentsIcon,
-    data: [
-      {
-        title: "Indexer",
-        path: "/references/indexer",
-      },
-      {
-        title: "Endpoints / Playground UIs",
-        path: "/references/indexer/endpoints",
-      },
-      {
-        title: "Querying",
-        path: "/references/indexer/querying",
-      },
-      {
-        title: "Versioning",
-        path: "/references/indexer/versioning",
-      },
-      {
-        title: "Entities",
-        path: "/references/indexer/entities",
-      }
-    ]
   }
 ]} />
 

pages/references/_meta.json

@@ -3,6 +3,5 @@
   "uagents": "Agents: uAgents Framework",
   "agentverse": "Agentverse",
   "ledger": "Ledger",
-  "cosmpy": "CosmPy API",
-  "indexer": "Indexer"
+  "cosmpy": "CosmPy API"
 }