feat: cleanup!

Author: drewstone

pages/developers/_meta.json

@@ -4,17 +4,15 @@
     "title": "Introduction"
   },
   "blueprints": "Blueprints",
-  "cli": "Tangle Blueprint CLI",
+  "cli": "Blueprint CLI",
   "-- gadget-tutorial": {
     "type": "separator",
     "title": "Blueprint Developers"
   },
-  "gadget-sdk": "Blueprint Gadget SDK",
-  "blueprint-macros": "Blueprint SDK Macros",
-  "blueprint-event-listeners": "Blueprint SDK Event Listeners",
-  "blueprint-contexts": "Blueprint SDK Contexts",
-  "p2p-networking": "Blueprint P2P Networking",
-  "tangle-avs": "Build a Tangle Blueprint AVS",
+  "gadget-sdk": "Introduction",
+  "blueprint-contexts": "Contexts",
+  "p2p-networking": "P2P Networking",
+  "tangle-avs": "Build a Tangle Blueprint",
   "eigenlayer-avs": "Build an Eigenlayer AVS",
   "testing-with-tangle": "Testing with Tangle",
   "troubleshooting": "Troubleshooting",

pages/developers/blueprint-contexts/introduction.mdx

@@ -4,81 +4,6 @@ title: Introduction to Contexts
 
 ## What is a Context?
 
-import TableOfContentCards from "../../../components/TableOfContentCards";
-
-<TableOfContentCards 
-  items={[
-    {
-      title: "Introduction to Contexts",
-      href: "/developers/blueprint-contexts/introduction",
-      subItems: [
-        {
-          title: "What is a Context?",
-          description: "Understanding the basics of Contexts in Gadget SDK"
-        },
-        {
-          title: "Why do we need Contexts?", 
-          description: "Benefits and use cases of the Context pattern"
-        },
-        {
-          title: "Built-in Contexts",
-          description: "Overview of provided Context implementations"
-        }
-      ]
-    },
-    {
-      title: "Keystore Context",
-      href: "/developers/blueprint-contexts/keystore-context",
-      subItems: [
-        {
-          title: "GenericKeyStore",
-          description: "Managing cryptographic keys and secrets"
-        }
-      ]
-    },
-    {
-      title: "EVM Provider Context",
-      href: "/developers/blueprint-contexts/evm-provider-context",
-      subItems: [
-        {
-          title: "EVM RPC Client",
-          description: "Interacting with EVM-compatible blockchains"
-        }
-      ]
-    },
-    {
-      title: "Tangle Client Context", 
-      href: "/developers/blueprint-contexts/tangle-client-context",
-      subItems: [
-        {
-          title: "Subxt Client",
-          description: "Interacting with the Tangle network"
-        }
-      ]
-    },
-    {
-      title: "Tangle Services Context",
-      href: "/developers/blueprint-contexts/services-context", 
-      subItems: [
-        {
-          title: "Service Properties",
-          description: "Accessing service instance details"
-        }
-      ]
-    },
-    {
-      title: "Eigenlayer Context",
-      href: "/developers/blueprint-contexts/eigenlayer-context",
-      subItems: [
-        {
-          title: "Eigenlayer Integration",
-          description: "Working with Eigenlayer services"
-        }
-      ]
-    }
-  ]}
-/>
-
 In the Gadget SDK, a Context holds utilities and dependencies that a job may need that aren't direct inputs. Think of it as a container for all the external resources and services your job requires to function.
 
 A Context can include various elements such as: