Nuxt AI Editor

nuxt-ai-editor

Vercel's Nuxt AI-powered Notion-like WYSIWYG editor — the Nuxt UI editor template: a Notion-like editor with rich text, tables, task lists, code blocks, slash commands, a drag handle, mentions, emoji and image uploads, plus AI inline completions and rewrites — running on Cloudflare Workers + Static Assets through Nitro's cloudflare_module preset, with its AI on Workers AI through the Worker's own binding and its images in an R2 bucket provisioned by Terraform through Orun, and packaged as an Orun baseline: one command takes a new editor from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing. Workers Free is enough: the Worker is about 2.6 MiB gzipped, under the plan's 3 MiB.

The template's code is the code. NuxtHub keeps its hub:blob with Cloudflare's driver — R2 in place of Vercel Blob — and the port changes what the Workers runtime and an unattended deployment force: the AI defaults to Workers AI, so a fresh product completes and rewrites text with no model key (the template's own AI Gateway model is used once its key is set, as in nuxt-ai-chatbot), and every icon the editor names is bundled with it. Real-time collaboration stays off, as upstream ships it. What the baseline adds is everything needed to make a copy of it somebody else's, built the way turso-starter is. See specs/epics/nuxt-ai-editor for the design, the milestones and the as-built status.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/nuxt-ai-editor
cd nuxt-ai-editor
orun new --blueprint repo-blueprint.yaml --out ~/sites/acme-notes --run-hooks --resume \
  --set reponame=acme-notes --set productname="Acme Notes" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → nuxt-ai-editor → Build). Two phases: 01-product creates the repository and lands the whole product as ONE pull request — intent, CI, tooling, the R2 root, the editor and its tests — and one convergence, per environment, applies the bucket, then deploys the editor with its name; 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

The new repository receives the product only — the app, its R2 root, its tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Cloudflare Worker and bucket names. None of this repository's machinery ships. No AI vendor key is asked for: the platform brokers none, and the editor runs on Workers AI.

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # render apps/web/wrangler.jsonc from the offline fixture
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # nuxt build → apps/web/.output (the Worker and its static assets)

pnpm --filter @app/web preview   # wrangler dev over the built Worker, on a local R2 bucket
pnpm --filter @app/web dev       # nuxt dev — the bindings through wrangler's platform proxy

Workers AI has no local mode: both reach it remotely, so wrangler login first.

How it maps to Vercel

How the bucket reaches the Worker

infra/terraform/cloudflare-r2 ──apply──► orun secret WIRING_CLOUDFLARE_R2 (stage, prod)
                                               │
                                               ▼
apps/web  dependsOn cloudflare-r2 (enforced on main)
          · secretEnv WIRING_CLOUDFLARE_R2_<ENV>
          · optionalSecretEnv the owner's AI Gateway key
  build:  tooling/wire/live.mjs → wrangler.jsonc with the environment's bucket
          (dev, verify-only, renders the fixture) → nuxt build (without the optional secret)
          → tooling/wire/worker-secrets.mjs → `wrangler secret bulk` (deploy lanes only)

wrangler.jsonc is committed as the fixture render of wrangler.template.jsonc, because the deploy lane's verify-app-structure step checks the config exists before it builds; testing/e2e.test.sh fails if the two disagree.

CI