Removing AI standalone section, moving MCP/Skills to product sections, updated About page

Author: brandonleekramer

nginx.conf

@@ -168,6 +168,12 @@ http {
         rewrite ^/docs/en/supported-networks/near/$                     $scheme://$http_host/docs/en/subgraphs/cookbook/near/                               permanent;
         rewrite ^/docs/en/tap/$                                         $scheme://$http_host/docs/en/indexing/tap/                                          permanent;
         rewrite ^/docs/en/tokenomics/$                                  $scheme://$http_host/docs/en/resources/tokenomics/                                  permanent;
+        rewrite ^/docs/en/ai-suite/ai-introduction/$                    $scheme://$http_host/docs/en/ai-overview/                                           permanent;
+        rewrite ^/docs/en/ai-suite/subgraph-skills/$                    $scheme://$http_host/docs/en/subgraphs/skills/                                      permanent;
+        rewrite ^/docs/en/ai-suite/subgraph-mcp/$                       $scheme://$http_host/docs/en/subgraphs/subgraph-mcp/                                permanent;
+        rewrite ^/docs/en/ai-suite/substreams-skills/$                  $scheme://$http_host/docs/en/substreams/skills/                                     permanent;
+        rewrite ^/docs/en/ai-suite/substreams-mcp/$                     $scheme://$http_host/docs/en/substreams/substreams-mcp/                             permanent;
+        rewrite ^/docs/en/ai-suite/$                                    $scheme://$http_host/docs/en/ai-overview/                                           permanent;
 
         # Token API redirects
         rewrite ^/docs/en/token-api/quick-start/$                       https://app.pinax.network/docs/api/                                                 permanent;

website/src/layout/Layout.tsx

@@ -180,6 +180,9 @@ export default function Layout({ pageOpts, children }: NextraThemeLayoutProps<Fr
         if (routeWithoutLocale === '/about' || routeWithoutLocale.startsWith('/about/')) {
           return <TheGraph alt="" />
         }
+        if (routeWithoutLocale === '/ai-overview' || routeWithoutLocale.startsWith('/ai-overview/')) {
+          return <TheGraph alt="" />
+        }
         if (routeWithoutLocale === '/supported-networks' || routeWithoutLocale.startsWith('/supported-networks/')) {
           return <Stack alt="" variant={selected ? 'fill' : 'regular'} />
         }

website/src/pages/en/about.mdx

@@ -5,35 +5,56 @@ description: This page summarizes the core concepts and basics of The Graph Netw
 
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data across [60+ networks](/supported-networks/).
+The Graph is a suite of blockchain data infrastructure products that extract, process, and deliver scalable blockchain data solutions across 60+ networks. The Graph enables application developers, data analysts, AI agents, and enterprise teams that need structured, reliable, and real-time access to blockchain data. Products include Subgraphs, Substreams, and Amp. As of early 2026, The Graph has served over 1.27 trillion queries to more than 75,000 projects, powered by 50+ independent Indexer nodes worldwide. To learn more about The Graph from a non-technical perspective, visit [The Graph Overview](https://thegraph.com/what-is-the-graph/).
 
-Its data services include:
+## The Graph's Core Products:
 
-- [Subgraphs](/subgraphs/developing/subgraphs/): Open APIs to query blockchain data that can be created or queried by anyone.
-- [Substreams](/substreams/introduction/): High-performance data streams for real-time blockchain processing, built with modular components.
+- [Subgraphs](/subgraphs/developing/subgraphs/): Custom open APIs that extract data from a blockchain, process it, and serve it via GraphQL. The original and most widely used data service on The Graph.
+- [Substreams](/substreams/introduction/): A parallel blockchain indexing technology for high-performance, real-time data streams. Built for use cases that need faster sync and larger throughput than traditional Subgraphs.
+- [Amp](https://ampup.sh/docs): A blockchain-native database designed to transform onchain activity into enterprise-ready datasets with built-in compliance, auditability, and verifiability.
 
-### Why Blockchain Data is Difficult to Query
+## Why Blockchain Data is Difficult to Index
 
-Reading data from blockchains requires processing smart contract events, parsing metadata from IPFS, and manually aggregating data.
+Blockchains are optimized for writing and verifying transactions, not for reading or analyzing them. This makes indexing on-chain data harder than it looks:
 
-The result is slow performance, complex infrastructure, and scalability issues.
+- **No relational structure:** Data is stored as an append-only chain of blocks with no tables, indices, or relationships. Answering "all transfers for this user" means scanning the chain block by block, which is slow and resource intensive.
+- **State isn't readable in useful forms:** Contract data lives in low-level storage slots and event logs, which must be reconstructed into meaningful application-readable format.
+- **No query language:** Blockchains expose only low-level RPC methods (`eth_getLogs`, `eth_call`), with no native way to filter, aggregate, sort, or join.
+- **Historical data needs archive nodes:** Querying past state requires expensive archive nodes, since most nodes prune historical data.
+- **Data is fragmented:** Real applications scatter data across many contracts and events that were never designed to be joined together.
+
+Doing this processing on demand is slow, and it forces every developer to build and maintain their own indexing infrastructure.
 
 ## How The Graph Solves This
 
-The Graph uses a combination of cutting-edge research, core dev expertise, and independent Indexers to make blockchain data accessible for developers.
+The Graph is a modular protocol whose data services each specialize in a different class of blockchain data problem. Rather than forcing every use case through a single tool, the protocol lets developers choose the right product or service for their use case:
+ 
+- **Specialized data services for specific use cases:** The protocol supports a spectrum of data services, each optimized for a distinct need. A team can use one service for custom application APIs, another for high-throughput streaming, and another for compliance-grade analytics, all secured by the same network.
+- **Subgraphs for resilient, decentralized APIs:** Subgraphs define exactly which contracts, events, and entities to index and how to transform raw on-chain data into structured entities queryable via GraphQL. Because a global network of Indexers serves this data, Subgraphs offer resilience and geographic diversification, with no single point of failure.
+- **Substreams for real-time scale:** Substreams use parallelized, streaming data processing to index at high throughput and deliver onchain data with low latency. This scales indexing far beyond sequential processing and powers real-time use cases such as live liquidity and trading data.
+- **Amp for verifiability and auditability:** Amp provides verifiable, enterprise-grade access to on-chain data with built-in audit trails, meeting the auditability and compliance requirements of regulated institutions.
+
+The result: raw, hard-to-access on-chain data becomes fast, structured, and ready to power applications—from a single dapp to institutional-scale systems.
+
+## Find the right product for your use case:
+
+### 1. Subgraphs: Custom APIs for Developers
+
+**Use Cases:** Best when an application needs its own structured, queryable data (specific contracts, events, entities) via an opinionated API. Ideal for DeFi dashboards, NFT marketplaces, governance UIs, and most dapp frontends.
 
-Find the perfect data service for you:
+- [Explore existing Subgraphs](https://thegraph.com/explorer)
+- [Build a Subgraph](/subgraphs/quick-start)
 
-### 1. Custom APIs for web3 Developers
+### 2. Substreams: Real-Time & Historical Data Streams
 
-**Use Case:** Dapp frontends, custom analytics.
+**Use Case:** Best when you need low-latency data at scale: live liquidity and price feeds, trading and liquidation events, analytics pipelines, and large-scale backfills across chains.
 
-- [Explore Subgraphs](https://thegraph.com/explorer)
-- [Build Your Subgraph](/subgraphs/quick-start)
+- [Browse existing Substreams](https://substreams.dev/)
+- [Build with Substreams](/substreams/introduction/)
 
-### 2. Real-Time & Historical Data Streams
+### 3. Amp: Verifiable, compliance-grade data
 
-**Use Case:** High-frequency trading, live analytics.
+**Use Case:** Best for regulated and institutional use cases needing SQL access and built-in audit trails: enterprise analytics, financial reporting, and workflows with regulatory requirements.
 
-- [Build Substreams](/substreams/introduction/)
-- [Browse Community Substreams](https://substreams.dev/)
+- [Contact Team](https://www.edgeandnode.com/)
+- [Get Started with Amp](https://ampup.sh/docs)

…rc/pages/en/ai-suite/ai-introduction.mdx website/src/pages/en/ai-overview.mdxwebsite/src/pages/en/ai-suite/ai-introduction.mdx renamed to website/src/pages/en/ai-overview.mdx website/src/pages/en/ai-suite/ai-introduction.mdx renamed to website/src/pages/en/ai-overview.mdx

@@ -23,7 +23,7 @@ Agent Skills extend AI coding assistants like Claude Code and Cursor with deep,
 
 ### Subgraph MCP
 
-The [Subgraph MCP](/ai-suite/subgraph-mcp/introduction/) server connects models to Subgraphs on The Graph Network. It allows language models to explore Subgraph schemas, execute GraphQL queries, find relevant Subgraphs by keyword or contract, and surface usage metrics using natural language.
+The [Subgraph MCP](/subgraphs/subgraph-mcp/introduction/) server connects models to Subgraphs on The Graph Network. It allows language models to explore Subgraph schemas, execute GraphQL queries, find relevant Subgraphs by keyword or contract, and surface usage metrics using natural language.
 
 #### Benefits of Using Subgraph MCP
 
@@ -34,7 +34,7 @@ The [Subgraph MCP](/ai-suite/subgraph-mcp/introduction/) server connects models
 
 ### Substreams MCP
 
-The [Substreams MCP](/ai-suite/substreams-mcp/search/) server lets AI agents search, inspect, and analyze Substreams packages — from registry discovery to sink deployment. It supports dual transport for local clients and SSE/HTTP for remote agents.
+The [Substreams MCP](/substreams/substreams-mcp/search/) server lets AI agents search, inspect, and analyze Substreams packages — from registry discovery to sink deployment. It supports dual transport for local clients and SSE/HTTP for remote agents.
 
 #### Tools
 
@@ -53,7 +53,7 @@ The [Substreams MCP](/ai-suite/substreams-mcp/search/) server lets AI agents sea
 
 ### Agent Skills for Subgraphs
 
-[Subgraph Skills](/ai-suite/subgraph-skills/) is a collection of AI agent skills that provide expert knowledge for developing, testing, and deploying Subgraphs. Skills are available as Claude Code plugins or OpenClaw skills.
+[Subgraph Skills](/subgraphs/skills/) is a collection of AI agent skills that provide expert knowledge for developing, testing, and deploying Subgraphs. Skills are available as Claude Code plugins or OpenClaw skills.
 
 #### Available Skills
 
@@ -65,7 +65,7 @@ The [Substreams MCP](/ai-suite/substreams-mcp/search/) server lets AI agents sea
 
 ### Agent Skills for Substreams
 
-[Substreams Skills](/ai-suite/substreams-skills/) enhance AI coding assistants with specialized Substreams expertise. Install once and your assistant automatically applies Substreams best practices when working on relevant projects.
+[Substreams Skills](/substreams/skills/) enhance AI coding assistants with specialized Substreams expertise. Install once and your assistant automatically applies Substreams best practices when working on relevant projects.
 
 #### Available Skills
 

website/src/pages/en/ai-suite/_meta-titles.json

@@ -1,4 +1,5 @@
 {
+  "subgraph-mcp": "Subgraph MCP",
   "querying": "Querying",
   "developing": "Developing",
   "guides": "How-to Guides",

website/src/pages/en/ai-suite/_meta.js

@@ -2,6 +2,8 @@ import titles from './_meta-titles.json'
 
 export default {
   'quick-start': '',
+  'subgraph-mcp': titles['subgraph-mcp'],
+  skills: '',
   explorer: '',
   querying: titles.querying ?? '',
   developing: titles.developing ?? '',