docs: migrate docs to Astro Starlight

.gitignore

@@ -2,8 +2,7 @@
 node_modules/
 .npm-cache/
 dist/
-docs/.vitepress/cache/
-docs/.vitepress/dist/
+docs/.astro/
 packages/*/dist/
 packages/*/temp/
 coverage/

README.md

@@ -33,5 +33,5 @@ Runnable examples live in [`examples/`](./examples/) and are indexed in [`exampl
 ## Docs
 
 - [Public Docs](https://execbox.aallam.com)
-- [Getting Started Guide](./docs/getting-started.md)
-- [Execbox Architecture Overview](./docs/architecture/README.md)
+- [Getting Started Guide](./docs/src/content/docs/getting-started.md)
+- [Execbox Architecture Overview](./docs/src/content/docs/architecture/index.md)

docs/astro.config.mjs

@@ -0,0 +1,76 @@
+import starlight from "@astrojs/starlight";
+import { defineConfig } from "astro/config";
+import mermaid from "astro-mermaid";
+
+export default defineConfig({
+  site: "https://execbox.aallam.com",
+  integrations: [
+    mermaid({
+      autoTheme: true,
+      enableLog: false,
+      mermaidConfig: {
+        securityLevel: "loose",
+      },
+    }),
+    starlight({
+      title: "execbox",
+      description:
+        "Portable code execution for MCP tools and wrapped MCP servers.",
+      customCss: ["/src/styles/custom.css"],
+      lastUpdated: true,
+      pagefind: true,
+      social: [
+        {
+          icon: "github",
+          label: "GitHub",
+          href: "https://github.com/aallam/execbox",
+        },
+      ],
+      sidebar: [
+        {
+          label: "Start",
+          items: [
+            { label: "Overview", link: "/" },
+            { label: "Getting Started", slug: "getting-started" },
+            { label: "Runtime Choices", slug: "runtime-choices" },
+          ],
+        },
+        {
+          label: "Use",
+          items: [
+            { label: "Examples", slug: "examples" },
+            {
+              label: "MCP Provider",
+              slug: "architecture/execbox-mcp-and-protocol",
+            },
+            {
+              label: "Remote Runner",
+              slug: "architecture/execbox-remote-workflow",
+            },
+          ],
+        },
+        {
+          label: "Understand",
+          items: [
+            { label: "Security", slug: "security" },
+            { label: "Architecture", slug: "architecture" },
+            { label: "Performance", slug: "performance" },
+          ],
+        },
+        {
+          label: "Reference",
+          items: [
+            {
+              label: "Protocol",
+              slug: "architecture/execbox-protocol-reference",
+            },
+            {
+              label: "Runner Specification",
+              slug: "architecture/execbox-runner-specification",
+            },
+          ],
+        },
+      ],
+    }),
+  ],
+});

docs/src/content.config.ts

@@ -0,0 +1,7 @@
+import { defineCollection } from "astro:content";
+import { docsLoader } from "@astrojs/starlight/loaders";
+import { docsSchema } from "@astrojs/starlight/schema";
+
+export const collections = {
+  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
+};

docs/architecture/execbox-core.md → docs/src/content/docs/architecture/execbox-core.md

@@ -1,4 +1,7 @@
-# Execbox Core Architecture
+---
+title: Execbox Core Architecture
+description: Provider resolution, execution contracts, shared runner semantics, and errors in execbox core.
+---
 
 This page covers the parts of execbox that stay stable regardless of which executor package you choose.
 

docs/architecture/execbox-executors.md → docs/src/content/docs/architecture/execbox-executors.md

@@ -1,4 +1,7 @@
-# Execbox Executors
+---
+title: Execbox Executors
+description: Compare inline QuickJS, worker-hosted QuickJS, and remote executor trade-offs.
+---
 
 This page explains how the available executors differ and what trade-offs they make.