@lukoweb/apitogo 0.1.102 → 0.1.104

package/dist/declarations/lib/components/SiteTitle.d.ts

@@ -2,5 +2,9 @@ type SiteTitleProps = {
     title: string;
     className?: string;
 };
+export declare const splitBrandWordmark: (title: string) => {
+    prefix: string;
+    accent: string | null;
+};
 export declare const SiteTitle: ({ title, className }: SiteTitleProps) => import("react/jsx-runtime").JSX.Element;
 export {};

package/docs/cli/commands.md

@@ -76,9 +76,9 @@ These print a redirect message — use the replacement:
 
 | Removed                     | Use instead                                           |
 | --------------------------- | ----------------------------------------------------- |
-| `preview`                   | `apitogo build --preview` or `apitogo run`            |
-| `remove`                    | `apitogo teardown --yes`                              |
-| `configure-github-workflow` | `apitogo deploy`                                       |
+| `preview`                   | `npx apitogo build --preview` or `npx apitogo run`    |
+| `remove`                    | `npx apitogo teardown --yes`                          |
+| `configure-github-workflow` | `npx apitogo deploy`                                   |
 
 ## Related
 

package/docs/cli/go-live.md

@@ -1,12 +1,12 @@
 ---
 title: Go live with CLI
 description:
-  Publish an APIToGo developer portal with apitogo deploy — platform plans, secrets, and status.
+  Publish an APIToGo developer portal with npx apitogo deploy — platform plans, secrets, and status.
 sidebar_icon: rocket
 ---
 
 **Go live** publishes your shaped portal to APItoGo hosting, optionally deploys the backend, upserts
-gateway plans, and verifies the live site. `apitogo deploy` is the source of truth; MCP
+gateway plans, and verifies the live site. `npx apitogo deploy` is the source of truth; MCP
 `publish_dev_portal` spawns the same CLI.
 
 ## Before you publish
@@ -40,11 +40,11 @@ gateway plans, and verifies the live site. `apitogo deploy` is the source of tru
 
 ```bash
 cd ./dev-portal
-apitogo deploy --platform-plan free
-apitogo status
+npx apitogo deploy --platform-plan free
+npx apitogo status
 ```
 
-`apitogo deploy`:
+`npx apitogo deploy`:
 
 - Creates or links the platform project
 - Provisions modules and syncs gateway plans
@@ -62,11 +62,11 @@ Do not treat warm-pool URLs as live until deploy and status succeed.
 ## Target specific resources
 
 ```bash
-apitogo deploy --only apihub
-apitogo deploy --only portal-backend
-apitogo deploy --only portal-frontend
-apitogo deploy --only apihub,portal-frontend
-apitogo deploy --only portal-frontend --force
+npx apitogo deploy --only apihub
+npx apitogo deploy --only portal-backend
+npx apitogo deploy --only portal-frontend
+npx apitogo deploy --only apihub,portal-frontend
+npx apitogo deploy --only portal-frontend --force
 ```
 
 | Resource         | What it updates                                      |
@@ -93,9 +93,9 @@ Resume state is stored in `.apitogo/publish-state.json`.
 ## After publish
 
 ```bash
-apitogo status              # account + project + live checks
-apitogo status --skip-live  # skip live health probes
-apitogo teardown --yes      # delete the platform project
+npx apitogo status              # account + project + live checks
+npx apitogo status --skip-live  # skip live health probes
+npx apitogo teardown --yes      # delete the platform project
 ```
 
 ## Platform plan vs API plans
@@ -109,7 +109,7 @@ apitogo teardown --yes      # delete the platform project
 
 | Path                    | Use when                                           |
 | ----------------------- | -------------------------------------------------- |
-| `apitogo deploy`         | Terminal, CI, scripts — full product go-live       |
+| `npx apitogo deploy`     | Terminal, CI, scripts — full product go-live       |
 | MCP `publish_dev_portal` | Agent-driven go-live with the same engine         |
 
 ## Related

package/docs/cli/overview.md

@@ -6,19 +6,19 @@ sidebar_icon: terminal
 ---
 
 The **`apitogo`** CLI lets you manage developer portals from the terminal. You scaffold and shape
-local files, preview with `apitogo run`, and publish to APItoGo hosting with `apitogo deploy`.
+local files, preview with `npx apitogo run`, and publish to APItoGo hosting with `npx apitogo deploy`.
 
 **First time?** Install and wire credentials → **[Install the CLI](./setup.md)**. Then follow
 [Shape](./shape.md) and [Go live](./go-live.md).
 
 ## What you get
 
-- Scaffold a local portal site (`npx @lukoweb/create-apitogo@latest` or `apitogo init`)
-- Shape backend, OpenAPI, plans, and docs pages via `apitogo config` and file edits
-- Preview locally (`apitogo run`)
-- Publish to APItoGo hosting (`apitogo deploy`) with platform plans **Free**, **Starter**, or
+- Scaffold a local portal site (`npx @lukoweb/create-apitogo@latest` or `npx @lukoweb/apitogo init`)
+- Shape backend, OpenAPI, plans, and docs pages via `npx apitogo config` and file edits
+- Preview locally (`npx apitogo run`)
+- Publish to APItoGo hosting (`npx apitogo deploy`) with platform plans **Free**, **Starter**, or
   **Professional**
-- Check live status (`apitogo status`) and tear down (`apitogo teardown --yes`)
+- Check live status (`npx apitogo status`) and tear down (`npx apitogo teardown --yes`)
 
 ## Prerequisites
 
@@ -40,17 +40,17 @@ local files, preview with `apitogo run`, and publish to APItoGo hosting with `ap
 
 | Approach | When it helps |
 | -------- | ------------- |
-| **`apitogo config`** | Wire OpenAPI, custom pages, gateway plans, and site title from the terminal. See [Make config](../configuration/make-config.mdx). |
+| **`npx apitogo config`** | Wire OpenAPI, custom pages, gateway plans, and site title from the terminal. See [Make config](../configuration/make-config.mdx). |
 | **Edit files directly** | Full control — `apitogo.config.json`, `pages/**`, `landing/LandingPage.tsx`, etc. |
 
 Common CLI shape tasks:
 
 | Change                              | How                                              |
 | ----------------------------------- | ------------------------------------------------ |
-| Backend runtime                     | `apitogo config` (backend)                       |
-| OpenAPI + API Reference nav         | `apitogo config` (openapi)                       |
-| Custom docs pages                   | `apitogo config` (page) or add under `pages/`    |
-| Gateway / API plans                 | `apitogo config` (plan) or edit manifest         |
+| Backend runtime                     | `npx apitogo config` (backend)                   |
+| OpenAPI + API Reference nav         | `npx apitogo config` (openapi)                   |
+| Custom docs pages                   | `npx apitogo config` (page) or add under `pages/` |
+| Gateway / API plans                 | `npx apitogo config` (plan) or edit manifest     |
 | Site title                          | `--title` or edit `apitogo.config.json`          |
 | Theme, fonts, branding, projectId   | Edit `apitogo.config.json`                       |
 
@@ -68,16 +68,16 @@ Details: [Manifest](../configuration/manifest.md).
 
 ## CLI vs MCP
 
-Both paths use the same config-first model. `apitogo deploy` runs the same engine as MCP
+Both paths use the same config-first model. `npx apitogo deploy` runs the same engine as MCP
 `publish_dev_portal`.
 
-| Task              | CLI                              | MCP (agent)                    |
-| ----------------- | -------------------------------- | ------------------------------ |
-| Scaffold          | `npm create` / `apitogo init`    | `create_dev_portal`            |
-| Shape config      | `apitogo config` + file edits    | `apply_product_intent` (shape) |
-| Preview           | `apitogo run`                    | `npm run dev` / preview tool   |
-| Publish           | `apitogo deploy`                  | `publish_dev_portal`           |
-| Status / teardown | `apitogo status` / `teardown`    | `verify_dev_portal_live` / `teardown_project` |
+| Task              | CLI                                      | MCP (agent)                    |
+| ----------------- | ---------------------------------------- | ------------------------------ |
+| Scaffold          | `npm create` / `npx @lukoweb/apitogo init` | `create_dev_portal`          |
+| Shape config      | `npx apitogo config` + file edits        | `apply_product_intent` (shape) |
+| Preview           | `npx apitogo run`                        | `npm run dev` / preview tool   |
+| Publish           | `npx apitogo deploy`                     | `publish_dev_portal`           |
+| Status / teardown | `npx apitogo status` / `npx apitogo teardown` | `verify_dev_portal_live` / `teardown_project` |
 
 Prefer MCP when an agent should drive changes. Prefer CLI for CI, scripts, or terminal-only
 workflows.

package/docs/cli/setup.md

@@ -6,35 +6,23 @@ sidebar_icon: terminal
 ---
 
 Use the **`apitogo`** CLI (`@lukoweb/apitogo`) to scaffold a local portal, shape
-`apitogo.config.json`, preview with `apitogo run`, and publish with `apitogo deploy`. Platform
+`apitogo.config.json`, preview with `npx apitogo run`, and publish with `npx apitogo deploy`. Platform
 commands (`deploy`, `status`, `teardown`) use the same engine as MCP `publish_dev_portal`.
 
+Examples in these docs use **`npx apitogo`** so they run the project-local CLI. A global install is
+optional and not required.
+
 ## Prerequisites
 
 - **Node.js 20+**
-- Platform API credentials from [apitogo.com](https://apitogo.com) when you run `apitogo deploy` (API
+- Platform API credentials from [apitogo.com](https://apitogo.com) when you run `npx apitogo deploy` (API
   key id + secret)
 
 ## Install
 
 The CLI is the npm package **`@lukoweb/apitogo`**. It exposes the **`apitogo`** binary. Scaffold
-commands add it to your project and `npm install` puts it on `node_modules/.bin`. A global install
-is optional.
-
-### Global install
-
-```bash
-npm install -g @lukoweb/apitogo
-```
-
-Then run `apitogo` from any directory:
-
-```bash
-apitogo --help
-```
-
-Upgrade later with `npm install -g @lukoweb/apitogo@latest`. Uninstall with
-`npm uninstall -g @lukoweb/apitogo`.
+commands add it to your project and `npm install` puts it on `node_modules/.bin`. Invoke it with
+`npx apitogo`.
 
 ### New project (recommended)
 
@@ -76,8 +64,8 @@ See `@lukoweb/create-apitogo --help` for package manager and install flags.
 
 ### Scaffold into an existing folder
 
-`apitogo init` writes `package.json` with `@lukoweb/apitogo` as a dependency. Run **`npm install`**
-before other `apitogo` commands:
+`npx @lukoweb/apitogo init` writes `package.json` with `@lukoweb/apitogo` as a dependency. Run **`npm install`**
+before other `npx apitogo` commands:
 
 ```bash
 npx @lukoweb/apitogo init ./dev-portal
@@ -87,24 +75,39 @@ npx apitogo config
 npm run dev
 ```
 
-`apitogo init` is local only — it does not call the platform. After `config`, run `npm run dev` to
-preview, then `apitogo deploy` when ready to go live.
+`npx @lukoweb/apitogo init` is local only — it does not call the platform. After `config`, run `npm run dev` to
+preview, then `npx apitogo deploy` when ready to go live.
 
 ### How to run `apitogo`
 
 | Situation                                                           | Command                                             |
 | ------------------------------------------------------------------- | --------------------------------------------------- |
 | After `npx @lukoweb/create-apitogo` or `npm install` in the project | `npx apitogo <command>` (e.g. `npx apitogo config`) |
-| Same, if `node_modules/.bin` is on your PATH                        | `apitogo <command>`                                 |
 | One-off, no project yet                                             | `npx @lukoweb/apitogo <command>`                    |
-| After [global install](#global-install)                             | `apitogo <command>` anywhere                        |
+| After [optional global install](#optional-global-install)           | `apitogo <command>` anywhere                        |
 
 `npm run dev` / `npm run build` use the project-local CLI via `package.json` scripts — no global
 install required.
 
+### Optional global install
+
+```bash
+npm install -g @lukoweb/apitogo
+```
+
+Then run `apitogo` from any directory:
+
+```bash
+apitogo --help
+```
+
+Upgrade later with `npm install -g @lukoweb/apitogo@latest`. Uninstall with
+`npm uninstall -g @lukoweb/apitogo`. Prefer `npx apitogo` in projects so each site uses the version
+in its `package.json`.
+
 ## Platform credentials
 
-Export these before `apitogo deploy`, `apitogo status`, or `apitogo teardown`:
+Export these before `npx apitogo deploy`, `npx apitogo status`, or `npx apitogo teardown`:
 
 | Variable             | Required | Purpose           |
 | -------------------- | -------- | ----------------- |
@@ -132,12 +135,12 @@ You should see `init`, `config`, `run`, `build`, `deploy`, `status`, and `teardo
 With credentials set:
 
 ```bash
-apitogo status
+npx apitogo status
 ```
 
 ## Next
 
 - [CLI overview](./overview.md)
 - [Shape](./shape.md) — scaffold and local preview
-- [Go live](./go-live.md) — `apitogo deploy`
+- [Go live](./go-live.md) — `npx apitogo deploy`
 - [Commands](./commands.md) — full catalog

package/docs/cli/shape.md

@@ -1,12 +1,12 @@
 ---
 title: Shape with CLI
 description:
-  Scaffold and customize a developer portal locally with apitogo init, apitogo config, and apitogo run.
+  Scaffold and customize a developer portal locally with npx apitogo init, config, and run.
 sidebar_icon: pencil-ruler
 ---
 
 **Shape** means: create or update a local portal site (OpenAPI, plans, docs pages, auth)
-without publishing. You preview with `apitogo run` or `npm run dev`.
+without publishing. You preview with `npx apitogo run` or `npm run dev`.
 
 Requires the **`apitogo`** CLI (`@lukoweb/apitogo`). If you have not installed it yet, see
 [Install the CLI](./setup.md).
@@ -32,11 +32,11 @@ npx apitogo config
 npm run dev
 ```
 
-`apitogo init` does **not** call the platform. Run `apitogo deploy` when you are ready to go live.
+`npx @lukoweb/apitogo init` does **not** call the platform. Run `npx apitogo deploy` when you are ready to go live.
 
-## Interactive config (`apitogo config`)
+## Interactive config (`npx apitogo config`)
 
-On a TTY, bare `apitogo config` opens the wizard. Each choice is written immediately; the loop
+On a TTY, bare `npx apitogo config` opens the wizard. Each choice is written immediately; the loop
 continues until you type `done`:
 
 | Choice | What it does |
@@ -46,7 +46,7 @@ continues until you type `done`:
 | `page` | Create `pages/<slug>.tsx` and wire it in navigation |
 | `plan` | Add a gateway plan (title, price, rate limit, monthly quota) |
 
-Authentication is **on by default** — the wizard does not ask for an auth API URL. `apitogo deploy`
+Authentication is **on by default** — the wizard does not ask for an auth API URL. `npx apitogo deploy`
 fills `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` after the portal backend exists.
 
 Fonts and colors are **not** prompted — edit `apitogo.config.json` or see
@@ -81,7 +81,7 @@ Common flags:
 
 ## Shape by editing files
 
-After `apitogo config`, edit the manifest and site files directly:
+After `npx apitogo config`, edit the manifest and site files directly:
 
 - **Plans, branding, backend, projectId** — `apitogo.config.json`
 - **Docs pages** — `pages/**/*.mdx` or `.tsx`
@@ -94,15 +94,15 @@ Never put OIDC or Stripe secrets in `apitogo.config.json`. Use `.env` with
 ## Preview locally
 
 ```bash
-apitogo run
-apitogo run --port 4000 --open
+npx apitogo run
+npx apitogo run --port 4000 --open
 ```
 
 Production build check:
 
 ```bash
-apitogo build
-apitogo build --preview
+npx apitogo build
+npx apitogo build --preview
 ```
 
 Shape-phase edits hot-reload when the dev server is running.
@@ -120,4 +120,4 @@ npm run dev
 
 ## Next
 
-When the site looks right, [go live](./go-live.md) with `apitogo deploy`.
+When the site looks right, [go live](./go-live.md) with `npx apitogo deploy`.

package/docs/configuration/authentication.md

@@ -24,13 +24,13 @@ Set authentication in `apitogo.config.json` (enabled by default on new scaffolds
 }
 ```
 
-Backend API URL (`apitogo deploy` writes this to `.env` after the portal backend is provisioned):
+Backend API URL (`npx apitogo deploy` writes this to `.env` after the portal backend is provisioned):
 
 ```bash
 VITE_APITOGO_AUTHENTICATION_API_BASE_URL=https://your-dev-portal-api.example.com
 ```
 
-You do not need to enter this URL in `apitogo config`. Or set `authentication.apiBaseUrl` in JSON /
+You do not need to enter this URL in `npx apitogo config`. Or set `authentication.apiBaseUrl` in JSON /
 `APITOGO_CONFIG_AUTHENTICATION__API_BASE_URL` in `.env` manually.
 
 ### Local demo mode

package/docs/configuration/make-config.mdx

@@ -7,7 +7,7 @@ description:
   site settings.
 ---
 
-The **`apitogo config`** (alias: `make-config`) command writes **`apitogo.config.json`**. It can scaffold a portal
+The **`npx apitogo config`** (alias: `make-config`) command writes **`apitogo.config.json`**. It can scaffold a portal
 project (package.json, tsconfig, landing and user-panel stubs, thin `apitogo.config.tsx`) when those
 files are missing, merge **site / theme / authentication** from flags, run an **interactive wizard**
 on a TTY (apply each change immediately), scan `pages/` for navigation, and wire OpenAPI plus an
@@ -23,8 +23,7 @@ Install the CLI first — see [Install the CLI](../cli/setup.md). In short:
 - **New site:** `npx @lukoweb/create-apitogo@latest` (installs `@lukoweb/apitogo` into the project)
 - **Existing folder:** `npx @lukoweb/apitogo init .` then `npm install`
 
-Run config from the project root with `npx apitogo config` (or `apitogo config` if
-`node_modules/.bin` is on your PATH).
+Run config from the project root with `npx apitogo config`.
 
 ## What it does
 
@@ -51,7 +50,7 @@ Run config from the project root with `npx apitogo config` (or `apitogo config`
 
 ## Interactive wizard
 
-On a TTY, bare `apitogo config` opens the wizard (no `-i` required). `-i` still works as an alias.
+On a TTY, bare `npx apitogo config` opens the wizard (no `-i` required). `-i` still works as an alias.
 Use `--no-interactive` (or pass flags like `--title`) for CI / non-TTY.
 
 ```bash
@@ -68,7 +67,7 @@ npx apitogo config
 2. **Wrap-up** — links to [docs.apitogo.com](https://docs.apitogo.com) for further configuration
 
 The wizard does **not** ask for fonts, colors, logo alt text, or the auth API base URL. Authentication
-stays **enabled**; `apitogo deploy` writes `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` to `.env` after
+stays **enabled**; `npx apitogo deploy` writes `VITE_APITOGO_AUTHENTICATION_API_BASE_URL` to `.env` after
 the portal backend is provisioned.
 
 If you add a **paid** plan (`priceAmount > 0`), the CLI warns that **Free platform hosting cannot

package/docs/configuration/manifest.md

@@ -64,7 +64,7 @@ metadata, with optional `.env` overrides for secrets and local tweaks.
 - **Site name / logo:** only `site.title` and `site.logo` (platform branding is derived at publish).
 - **OpenAPI path:** `backend.openApiPath` is derived from `apis[0].input`.
 - **Billing / account plans:** use `modules.userPanel.plans.enabled` and store the plan catalog in
-  `modules.userPanel.plans.items`. Add plans with `apitogo config` or edit the manifest by hand.
+  `modules.userPanel.plans.items`. Add plans with `npx apitogo config` or edit the manifest by hand.
   See [Gateway plans](./plans.md). Legacy root `plans` is migrated on load.
 - **Docs / API keys:** configure under `modules.docs` and `modules.userPanel.apiKeys` only.
 - **Gateway:** top-level `gateway` (not under `authentication`). See [Gateway CORS](#gateway-cors)
@@ -96,7 +96,7 @@ when tenant apps or local frontends call the gateway:
 | Wildcard | `"*"` is allowed (replaces the list; credentials stay off). |
 | Empty / omitted | Portal playground still works; only extras are missing. |
 
-Apply with `apitogo deploy` / `publish_dev_portal` so APIM policies pick up the change.
+Apply with `npx apitogo deploy` / `publish_dev_portal` so APIM policies pick up the change.
 
 ## Environment variables
 

package/docs/configuration/navigation.mdx

@@ -58,7 +58,7 @@ one of several types. At the simplest level you may only have links and categori
 
 ## Generate navigation automatically
 
-Use the CLI command **`apitogo make-config`** to merge **`navigation`** from your pages folder into
+Use the CLI command **`npx apitogo make-config`** to merge **`navigation`** from your pages folder into
 `apitogo.config.json`. See **[Make config (CLI)](./make-config.md)** for usage. The command does **not**
 change **`redirects`**.
 

package/docs/configuration/overview.md

@@ -160,7 +160,7 @@ Put navigation in `apitogo.config.json`, or keep large trees in a separate modul
 ## Related
 
 - [Manifest (`apitogo.config.json`)](./manifest.md)
-- [Make config (CLI)](./make-config.mdx) — interactive wizard (`apitogo config`)
+- [Make config (CLI)](./make-config.mdx) — interactive wizard (`npx apitogo config`)
 - [Gateway plans](./plans.md)
 - [Authentication](./authentication.md)
 - [MCP overview](../mcp/overview.md)

package/docs/configuration/plans.md

@@ -12,13 +12,13 @@ description:
 - **`/account/plans`** — authenticated billing. Sign-in required. Manage and change subscriptions.
 
 They are separate from **platform hosting** (Free / Starter / Professional on APItoGo), which you
-select with `apitogo deploy --platform-plan`.
+select with `npx apitogo deploy --platform-plan`.
 
 Store the catalog under `modules.userPanel.plans.items` in `apitogo.config.json`.
 
 ## Shape with the CLI
 
-`apitogo config` can add plans interactively (title, price, rate limit, monthly quota). Each plan is
+`npx apitogo config` can add plans interactively (title, price, rate limit, monthly quota). Each plan is
 written immediately. You can also edit the manifest by hand or use MCP `update_dev_portal_manifest`.
 
 ```bash
@@ -92,17 +92,17 @@ After OpenAPI is deployed, you can scope a plan to specific operations with
 Gateway plans are applied when you run:
 
 ```bash
-apitogo deploy
+npx apitogo deploy
 ```
 
-`apitogo deploy` syncs plans from the manifest to the platform gateway. Paid plans require Stripe
+`npx apitogo deploy` syncs plans from the manifest to the platform gateway. Paid plans require Stripe
 secrets in `.env` before publish — see [Go live with CLI](../cli/go-live.md).
 
 ## Platform hosting vs gateway plans
 
 | Kind | What it is | How |
 | ---- | ---------- | --- |
-| **Platform hosting** | APItoGo bill for hosting your portal + API hub | `apitogo deploy --platform-plan` |
+| **Platform hosting** | APItoGo bill for hosting your portal + API hub | `npx apitogo deploy --platform-plan` |
 | **Gateway / API plans** | What your customers pay for API access | `modules.userPanel.plans.items` |
 
 ### Free platform limitations
@@ -113,7 +113,7 @@ The **Free** platform plan cannot:
 - Attach a **custom domain** to the dev portal
 
 Use **Starter** or **Professional** for paid API tiers, Stripe checkout, and custom domains. If your
-manifest has paid plans and you try `apitogo deploy --platform-plan free`, apply is blocked until you
+manifest has paid plans and you try `npx apitogo deploy --platform-plan free`, apply is blocked until you
 upgrade or zero/remove those paid plans.
 
 ## Related

package/docs/deploy/apitogo.md

@@ -1,6 +1,6 @@
 # Deploy with APIToGo CLI
 
-Platform publish is **`apitogo deploy`** — the same engine as MCP `publish_dev_portal`.
+Platform publish is **`npx apitogo deploy`** — the same engine as MCP `publish_dev_portal`.
 
 Full walkthrough (prerequisites, secrets, `--only`, status, teardown):
 
@@ -12,6 +12,6 @@ Quick reference:
 export APITOGO_API_KEY_ID=apk_...
 export APITOGO_API_SECRET=...
 cd ./dev-portal
-apitogo deploy --platform-plan free
-apitogo status
+npx apitogo deploy --platform-plan free
+npx apitogo status
 ```

package/docs/deployment.md

@@ -2,7 +2,7 @@
 
 | Path | Docs |
 | --- | --- |
-| **CLI** (`apitogo deploy`) | [Go live with CLI](./cli/go-live.md) |
+| **CLI** (`npx apitogo deploy`) | [Go live with CLI](./cli/go-live.md) |
 | **MCP / agents** | [Go live](./mcp/go-live.md) |
 
-Local-only builds: `apitogo build` (optional `--preview`). Platform publish is always `apitogo deploy`.
+Local-only builds: `npx apitogo build` (optional `--preview`). Platform publish is always `npx apitogo deploy`.

package/docs/guides/custom-pages.md

@@ -13,7 +13,7 @@ Start by creating the page you want to add.
 
 ## CLI scaffold
 
-`apitogo config` can create a starter page under `pages/` and wire it into navigation immediately.
+`npx apitogo config` can create a starter page under `pages/` and wire it into navigation immediately.
 Choose `page` in the wizard loop, then edit the generated `.tsx` file.
 
 Predefined UI components (Callout, Card, Button, Heading, and more) are documented under

package/docs/guides/environment-variables.md

@@ -21,7 +21,7 @@ APIToGo uses Vite’s [env and mode](https://vite.dev/guide/env-and-mode) model,
 Nested overrides use `__` path segments (SCREAMING_SNAKE). See [Manifest](../configuration/manifest.md).
 
 **Never commit** OIDC client secrets or Stripe keys. MCP never puts secrets in chat — you write them
-to `.env` before [go-live](../mcp/go-live.md) or `apitogo deploy` ([CLI go-live](../cli/go-live.md)).
+to `.env` before [go-live](../mcp/go-live.md) or `npx apitogo deploy` ([CLI go-live](../cli/go-live.md)).
 
 Example:
 

package/docs/markdown/frontmatter.md

@@ -122,8 +122,8 @@ draft: true
 
 When `draft: true` is set:
 
-- The document will be visible when running `apitogo run`
-- The document will be excluded from builds created with `apitogo build`
+- The document will be visible when running `npx apitogo run`
+- The document will be excluded from builds created with `npx apitogo build`
 - The document won't appear in the navigation or be accessible via URL in production
 
 :::

package/docs/mcp/go-live.md

@@ -88,7 +88,7 @@ shape → deploy_backend → publish_dev_portal(skipBackendRedeploy: true)
 | Path                         | Use when                                              |
 | ---------------------------- | ----------------------------------------------------- |
 | MCP `publish_dev_portal`     | Full product go-live (plans, auth, hosting, verify)   |
-| CLI `apitogo deploy`          | Publish config to platform (apihub + portal)          |
+| CLI `npx apitogo deploy`      | Publish config to platform (apihub + portal)          |
 
 See [Go live with CLI](../cli/go-live.md).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lukoweb/apitogo",
-  "version": "0.1.102",
+  "version": "0.1.104",
   "type": "module",
   "sideEffects": [
     "**/*.css",
@@ -23,8 +23,8 @@
     "docs"
   ],
   "bin": {
-    "zudoku": "./cli.js",
-    "apitogo": "./cli.js"
+    "apitogo": "./cli.js",
+    "zudoku": "./cli.js"
   },
   "exports": {
     ".": {

package/src/lib/components/Header.tsx

@@ -176,7 +176,7 @@ export const Header = memo(function HeaderInner() {
             <Link
               to={site?.logo?.href ?? "/"}
               reloadDocument={site?.logo?.reloadDocument ?? true}
-              className="shrink-0"
+              className="shrink-0 no-underline"
             >
               <div className="flex items-center gap-3.5">
                 {site?.logo ? (
@@ -200,9 +200,7 @@ export const Header = memo(function HeaderInner() {
                     ) : null}
                   </>
                 ) : (
-                  <span className="text-xl font-bold tracking-tight">
-                    {site?.title}
-                  </span>
+                  <SiteTitle title={site?.title ?? ""} />
                 )}
               </div>
             </Link>

package/src/lib/components/SiteTitle.tsx

@@ -5,16 +5,28 @@ type SiteTitleProps = {
   className?: string;
 };
 
+const API_SUFFIX = /^(.*?)(?:\s*)(API)$/i;
+
+export const splitBrandWordmark = (title: string) => {
+  const match = title.trim().match(API_SUFFIX);
+  if (!match?.[1]) {
+    return { prefix: title, accent: null as string | null };
+  }
+  return { prefix: match[1], accent: match[2] ?? "API" };
+};
+
 export const SiteTitle = ({ title, className }: SiteTitleProps) => {
+  const { prefix, accent } = splitBrandWordmark(title);
+
   return (
-    <div
+    <span
       className={cn(
-        "shrink-0 font-bold text-[19px] tracking-[-0.02em] text-foreground",
+        "font-sans text-[1.4rem] font-extrabold tracking-[-0.03em] text-foreground",
         className,
       )}
-      style={{ fontFamily: '"Space Grotesk", var(--font-sans, sans-serif)' }}
     >
-      {title}
-    </div>
+      {prefix}
+      {accent ? <span className="text-primary">{accent}</span> : null}
+    </span>
   );
 };