@lukoweb/apitogo 0.1.66 → 0.1.68

package/docs/quickstart.md

@@ -1,87 +1,82 @@
 ---
 title: Quickstart
 description:
-  Get started with APIToGo by creating a new APIToGo app using the `@lukoweb/create-apitogo` tool.
+  Get started with APIToGo MCP — connect your agent, shape a portal, and preview locally.
 sidebar_icon: circle-play
-zuplo: false
 ---
 
-Ready to build beautiful API documentation and developer portals in minutes? APIToGo's CLI tool will
-have you up and running with a modern, customizable site that your developers will love.
+Build an API product (developer portal, plans, gateway, backend) with an AI agent and the
+**APItoGo MCP** server. Works with Cursor, Claude, Codex, and other MCP hosts.
 
 ## Prerequisites
 
-- **Node.js** `22.7.0+` (or `20.19+`) - [Download here](https://nodejs.org/)
-- A terminal or command prompt
-- Your favorite code editor
+- **Node.js 20+** on the agent machine
+- An MCP-capable agent (Cursor, Claude Desktop / Claude Code, Codex, …)
+- Platform API keys from [apitogo.com](https://apitogo.com)
 
-## Getting Started
+## Get started
 
 <Stepper>
 
-1. **Create your new APIToGo project:**
+1. **Create API credentials**
 
-   ```bash
-   npm create @lukoweb/apitogo@latest
-   ```
+   In the [APItoGo dashboard](https://apitogo.com), create an API key and copy the **key id** and
+   **secret**.
 
-   The CLI will walk you through setting up your project with interactive prompts. By default you
-   get an empty dev-portal site; opt in to include starter example docs and an OpenAPI spec.
+1. **Configure MCP in your agent**
 
-1. **Navigate to your project:**
+   Wire `@lukoweb/apitogo-mcp` with your keys. Paste-ready snippets for **Cursor**, **Claude
+   Desktop**, **Claude Code**, **Codex**, and other hosts:
 
-   ```bash
-   cd your-project-name
-   ```
+   → **[Configure MCP in your agent](./mcp/setup.md)**
 
-1. **Launch the development server:**
+   Verify with `whoami` or by listing APItoGo tools.
 
-   ```bash
-   npm run dev
-   ```
+1. **Shape a product**
 
-   🎉 **That's it!** Your APIToGo site is now running at `http://localhost:3000`. You'll see hot
-   reloading as you make changes, so you can iterate quickly.
+   Ask your agent something like:
 
-1. **What's next?**
-   - Customize your [theme and colors](./customization/colors-theme.mdx)
-   - Add your [OpenAPI specifications](./configuration/api-reference.md)
-   - Set up [authentication](./configuration/authentication.md)
-   - [Deploy your site](./deployment.md) when you're ready to go live
+   > Create a portal in `./dev-portal` for my API in `./api` with Free (100/min) and Pro (1000/min);
+   > make `/health` public.
 
-</Stepper>
+   The agent should call `apply_product_intent` with `mode: "shape"` (or `create_dev_portal` for an
+   empty scaffold). See [Shape](./mcp/shape.md).
+
+1. **Preview locally**
 
-## Use an existing folder (Markdown and OpenAPI)
+   ```bash
+   cd ./dev-portal
+   npm run dev
+   ```
 
-If you already have **`.md` / `.mdx`** files and an **OpenAPI** spec in a project directory, you can
-add APIToGo without starting from `create-apitogo`:
+   Open `http://localhost:3000`. Iterate with MCP tools (pages, OpenAPI, theme, plans). Customize
+   the home page in `landing/LandingPage.tsx` when you have real copy.
 
-1. **Lay out content in a predictable way** — Put docs under a single folder (default name
-   **`pages/`**). Place your OpenAPI file where the tooling can find it, for example
-   **`apis/openapi.json`** or **`openapi.json`** in the project root.
+1. **Go live when ready**
 
-2. **Install the CLI** (once per machine), then run **`make-config`** from that project root:
+   Save OIDC (and Stripe if you have paid plans) in the site `.env`, then ask the agent to publish
+   — see [Go live](./mcp/go-live.md). Never paste secrets into chat.
 
-   ```bash
-   npm install -g @lukoweb/apitogo@latest
-   apitogo make-config
-   ```
+</Stepper>
 
-   This can create **`package.json`**, **`tsconfig.json`**, and **`apitogo.config.tsx`** when
-   missing, add an **`apis`** entry when a spec is detected, and generate **`navigation`** and
-   **`redirects`** from your Markdown tree.
+## What's next
 
-3. **Install dependencies and start dev** (if `package.json` was just created):
+- [Configure MCP](./mcp/setup.md) — agent-specific install
+- [MCP overview](./mcp/overview.md) — what the server does
+- [Shape](./mcp/shape.md) · [Go live](./mcp/go-live.md) · [Tools](./mcp/tools.md)
+- [Manifest](./configuration/manifest.md) · [Authentication](./configuration/authentication.md)
 
-   ```bash
-   npm install
-   npm run dev
-   ```
+## Without an agent (CLI)
 
-For options (for example `--pages-dir` if your docs are not under `pages/`) and full behavior, see
-**[Make config (CLI)](./configuration/make-config.mdx)**.
+If you prefer not to use MCP:
 
-## 🚀 Pro Tips
+```bash
+npm create @lukoweb/apitogo@latest
+cd your-project-name
+npm run dev
+```
 
-- Use `npm run build` to create a production build
-- Join our [Discord community](https://apitogo.com) for support and tips
+For an existing `pages/` + OpenAPI folder: `apitogo make-config` (see
+[Make config](./configuration/make-config.mdx)). Portal sites still need `apitogo.config.json` —
+[Manifest](./configuration/manifest.md). Site-only deploy with a token:
+[Deploy with APIToGo CLI](./deploy/apitogo.md).

package/docs/writing.mdx

@@ -30,7 +30,7 @@ Your content goes here using standard Markdown syntax.
 To make your documentation discoverable, add it to the navigation configuration. Documents are
 referenced by their file path:
 
-```ts title="apitogo.config.ts"
+```ts title="config"
 const config = {
   navigation: [
     {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lukoweb/apitogo",
-  "version": "0.1.66",
+  "version": "0.1.68",
   "type": "module",
   "sideEffects": [
     "**/*.css",

package/src/vite/plugin-config.ts

@@ -77,8 +77,11 @@ import { runPluginTransformConfig } from "@lukoweb/apitogo/plugins";
 
 const embeddedConfig = ${serializeClientConfig(loadedConfig)};
 
+// JSON embedding drops Symbol values (React element's $$typeof). Prefer live
+// navigation/plugins from the TSX module so custom-page elements stay valid.
 const config = await runPluginTransformConfig({
   ...embeddedConfig,
+  navigation: rawConfig?.navigation ?? embeddedConfig.navigation,
   plugins: rawConfig?.plugins ?? embeddedConfig.plugins ?? [],
   __meta: ${JSON.stringify(clientMeta)},
 });

package/docs/guides/navigation-migration.md

@@ -1,87 +0,0 @@
----
-title: Navigation Migration
-navigation_icon: arrow-right-left
----
-
-This guide explains how to migrate existing configurations that used `topNavigation`, `sidebar` and
-`customPages` to the new unified `navigation` configuration introduced in vNEXT.
-
-## Overview
-
-Navigation is now configured through a single `navigation` array. Items at the root level become top
-navigation tabs, while nested categories automatically form the sidebar. Custom pages are added
-using the `custom-page` item type.
-
-## Before and After
-
-```tsx title="Before"
-const config: ApitogoConfig = {
-  topNavigation: [
-    { id: "docs", label: "Docs" },
-    { id: "api", label: "API" },
-  ],
-  sidebar: {
-    docs: [{ type: "doc", id: "introduction" }],
-  },
-  customPages: [{ path: "/playground", render: Playground, prose: false }],
-  apis: {
-    type: "file",
-    input: "./openapi.json",
-    navigationId: "api",
-  },
-};
-```
-
-```tsx title="After"
-const config: ApitogoConfig = {
-  navigation: [
-    {
-      type: "category",
-      label: "Docs",
-      items: ["introduction"],
-    },
-    {
-      type: "custom-page",
-      path: "/playground",
-      element: <Playground />,
-    },
-    {
-      type: "link",
-      to: "/api",
-      label: "API",
-    },
-  ],
-  apis: [
-    {
-      path: "/api",
-      type: "file",
-      input: "./openapi.json",
-    },
-  ],
-};
-```
-
-## Migration steps
-
-<Stepper>
-
-1. **Create a `navigation` array**
-
-   Move all items from `topNavigation` and your sidebar into a new `navigation` array.
-
-1. **Convert custom pages**
-
-   Replace entries in `customPages` with `type: "custom-page"` items inside `navigation`.
-
-1. **Update plugin configs**
-
-   Replace all uses of `navigationId` with `path` in plugin options like `apis` or `catalogs`.
-   Navigation items of type `link` should use the `to` property to reference the path of the API or
-   catalog.
-
-1. **Reference plugin paths in navigation**
-
-   Items produced by plugins are not added automatically. Add links or categories in your
-   `navigation` so users can access them.
-
-</Stepper>