Rebrand Prisma Next to Prisma 8 across docs, blog, and site (#8117)

* Rebrand Prisma Next to Prisma 8 across docs, blog, and site

The early-access major version keeps its working-name identifiers but is
now called Prisma 8 everywhere users read it:

- All prose, frontmatter, changelog entries, and UI labels (docs version
  dropdown now "v8 (Early Access)"; sidebar matchers keep URL fallbacks).
- Reworded ~35 now-redundant "becomes Prisma 8 at GA" sentences and the
  announcement post's naming section; added a one-line editor's note to
  the nine posts that were about Prisma Next under its working name.
- Replaced 14 images carrying the old wordmark: outlined badge/headline
  text in the teal covers swapped for live Mona Sans text, the indigo
  announcement family (incl. roadmap, TS-migrations, EA meta and the
  docs sidebar banner) rebuilt from the announcement SVG, and metas
  re-rendered from their heroes. Hero-image skill logos renamed to
  prisma-8-*.
- Fixed 27 links pointing at renamed heading anchors.

Deliberately unchanged (product-owned identifiers and live URLs):
create prisma@next npm dist-tags, the prisma-next CLI and config file,
the @prisma-next/* npm scope, /docs/orm/next URL segments (GA cutover
plan in next.config.mjs), published blog slugs, pris.ly/pn-* links,
Discord #prisma-next channels, and the EA banner CSS selectors that
PostHog CTA actions target.

Verified: types:check (docs, blog), lint:links, lint:agent-ready,
test:llm-markdown, lint:spellcheck, pnpm check, plus rendered-page and
image review on dev servers. Pre-commit hook skipped (pnpm is not
callable in this non-interactive shell); its check command was run
manually and passed.

* Reframe Prisma 8 status from Early Access to Release Candidate

Everywhere the site describes Prisma 8's current stage now says the
Release Candidate is available instead of Early Access:

- Docs: the EA banner, the version dropdown ("v8 (RC)"), section
  meta.json titles, llms.txt topics, the standard "Prisma 8 is in Early
  Access" callout on nine pages, and status prose across the next tree.
- New "release-candidate" badge type (badge-types.ts drives the zod
  enum, label, and color maps); the 41 Prisma 8 pages switched to it.
  Other products keep the early-access badge (e.g. the Postgres
  serverless driver) and the generic maturity-tier docs are untouched.
- Blog: the "Looking ahead" footers, per-post status notes, and
  pris.ly/pn-ea link text; site stack page descriptions.

Kept as historical artifacts: the Early Access announcement post
(title, slug, cover, body), launch-story references to it, dated
changelog entries, the April roadmap metaDescription, and every other
product's Early Access mentions.

Verified: docs types:check, lint:links, lint:agent-ready,
test:llm-markdown, lint:spellcheck, pnpm check, and rendered-page
checks on dev servers (banner, dropdown, callouts, footers, ltree
heading). Pre-commit hook skipped; its check command was run manually
and passed.

* Move Prisma 8 docs from /next to /v8 and adopt ADR 242 package names

URL rename: the /next version segment (a working-name artifact) becomes
/v8 across all four trees: /orm/next -> /orm/v8, /cli/next -> /cli/v8,
/guides/next -> /guides/v8, and the getting-started tree /next -> /v8.
Content directories moved with git mv; every internal link, url:
frontmatter field, meta.json entry, llms.txt prefix and section slug
(/docs/llms/v8.txt), sidebar matcher, badge-visibility path, and the
version key ("next" -> "v8" in version.ts, the switcher, and the
sidebar tree) updated to match. Permanent redirects cover the old URLs,
including /llms/next.txt; the commented GA cutover map now speaks v8.

Package rename (ADR 242, prisma/prisma#29864): app-facing installs and
imports move from the @prisma-next scope to the consolidated @prisma
facades. Mappings verified against the merged monorepo's converted
example apps and facade export maps, e.g.:
- @prisma-next/postgres -> @prisma/orm-postgres (one dependency)
- @prisma-next/sql-runtime -> @prisma/orm-postgres/family-runtime
- @prisma-next/sql-orm-client -> @prisma/orm-postgres/orm-client
- @prisma-next/mongo-query-builder -> @prisma/orm-mongo/query-builder
- @prisma-next/target-postgres/migration -> @prisma/orm-postgres/target/migration
- @prisma-next/middleware-cache -> @prisma/orm-extension-middleware-cache
- extensions -> @prisma/orm-extension-{pgvector,postgis,paradedb,supabase,arktype-json}
Extension source links now point at prisma/prisma's
packages/3-extensions (verified to exist there).

Unchanged on purpose: the prisma-next bin and prisma-next.config.ts
(the Slack announcement defers that rename to a pre-RC roadmap task),
npm create prisma@next, blog slugs, pris.ly short links, and
prisma/prisma-next repo links whose targets have no equivalent in the
monorepo (retail-store example, planning docs).

Verified: docs types:check, lint:links (0 errors across the moved
trees), lint:agent-ready, test:llm-markdown, lint:spellcheck, pnpm
check; rendered /orm/v8 page with v8 (RC) dropdown and collapsed
sidebar; 308 redirects confirmed for all old-URL forms. Pre-commit hook
skipped; its check command was run manually and passed.

* feat(docs): add Prisma Composer section and move Prisma 8 CLI docs to the unified CLI

Adds a top-level Composer docs section (15 pages, Early Access): quickstart,
concepts (apps/modules, contracts, service input, databases, object storage,
building blocks), workflows (local dev, testing, deploying, porting), and
reference. Registered in the root meta.json, the navbar, and llmsSections.

Rewrites the cli/v8 tree from the standalone prisma-next binary to the
unified Prisma CLI (npx @prisma/cli@next until the prisma@next tag lands),
with command surfaces verified against 8.0.0-rc.2: init becomes orm init,
migration apply becomes migrate, migration ref becomes ref.

Composer commands were tested end to end locally (dev, log, watch-restart,
service-key 401s); deploy wording follows the composer repo guides.

* docs(v8): move guides, quickstarts, ORM, and Studio pages to the unified CLI

Replaces prisma-next invocations with npx @prisma/cli@next across the
Prisma 8 getting-started funnel, add-to-existing-project and import
guides, the ORM v8 concept/migrations/contract-authoring trees, the
Studio Prisma 8 page, the Deno guide, and the agent prompt blocks,
applying the verified command renames (init -> orm init).

Left untouched on purpose: quoted CLI output (the bundled toolchain
still prints prisma-next in hints), skill names, repo and blog URLs,
prisma-next.config.ts / prisma-next.md file names, and listings of
scaffold-generated files, which orm init still emits in that form. The
generated error reference is owned by the upstream sync.

* docs(v8): move Compute and blog to the unified CLI, consolidate skills, version the CLI section

Compute: rewrites the section around the unified CLI's real surface
(verified against @prisma/cli@next 8.0.0-rc.2): app -> service +
service deployment/domain, database -> postgres, the new bucket group,
and the changed deploy model, where deployments come from a git push,
the Console, or Composer rather than a CLI app deploy, and promote
rebuilds with production env vars. Drops the beta-only error-code
tables in favor of the verified dotted-code envelope.

Blog: swaps prisma-next invocations to npx @prisma/cli@next in the
four posts that show runnable commands.

Skills: the twelve prisma-next-* skills were consolidated upstream
into one prisma-8 skill in prisma/prisma/skills; updates the skills
page (install command and table) and every Prompt-your-coding-agent
section to reference prisma-8.

CLI versioning: the CLI section's version dropdown now lists v6, and
any pre-v8 selection resolves to the classic prisma CLI tree instead
of jumping to that version's ORM docs.

The /prisma-compute/deploy funnel page keeps the old flow on purpose;
it is being rebuilt around Composer in a parallel stream.

* docs(compute): move the deploy quickstart to the unified CLI's push flow

Rewrites /prisma-compute/deploy around the real deploy model: init +
project create + git connect, then push, with service show/open and
build logs for verification and promote/rollback for shipping. The
create-prisma path now hands off to the GitHub connection instead of
the removed app deploy loop, and the agent prompt teaches the new
command set.

* chore(docs): add savepoint to the spellcheck dictionary

* docs: point the spellcheck ignore at the moved error reference

The generated error reference moved to orm/v8 with the docs tree, but
the cspell ignore still named the old orm/next path, so the file's
generated vocabulary failed the full spellcheck run.

---------

Co-authored-by: Ankur Datta <64993082+ankur-arch@users.noreply.github.com>

Author: nurul3101

.claude/CLAUDE.md

@@ -58,7 +58,7 @@ Prisma documentation site built with **Fumadocs** on **Next.js 16 App Router**.
 - `content/docs/` - v7 documentation (latest), served at `/docs/v7/*`
 - `content/docs.v6/` - v6 documentation, served at `/docs/v6/*`
 - Each section has a `meta.json` defining page order, icons, and hierarchy
-- MDX frontmatter supports `badge: "early-access" | "deprecated" | "preview"`
+- MDX frontmatter supports `badge: "early-access" | "release-candidate" | "beta" | "deprecated" | "preview"`
 
 **Key Directories:**
 

.claude/skills/README.md

@@ -30,7 +30,7 @@ Produces a blog-post **skeleton** (frontmatter, section headings, short stubs),
 2. Point it at your local checkout of this repo so it can read current blog conventions.
 3. Give it your author slug. If you're a first-time author, it scaffolds an author profile too.
 4. Confirm the proposed slug, filename, date, and frontmatter.
-5. It writes the skeleton, then adds contextual links: the first mention of Prisma Postgres, Prisma Compute, and Prisma Next links to docs for SEO, and topic mentions cross-link to related posts (for example, a bloom-filter mention links to the bloom-index post).
+5. It writes the skeleton, then adds contextual links: the first mention of Prisma Postgres, Prisma Compute, and Prisma 8 links to docs for SEO, and topic mentions cross-link to related posts (for example, a bloom-filter mention links to the bloom-index post).
 6. It hands back a link inventory and a next-step reminder. You flesh out the prose and open a draft PR.
 
 **Note:** the skill reads `content-write-blog/assets/positioning.md`, Prisma's internal positioning doc. It is **not committed to this public repo** (it's gitignored). Place it locally before drafting, or the skill will ask for it.

.claude/skills/content-create-hero-image/README.md

@@ -104,5 +104,5 @@ Mono for code/data. No stock imagery, generic AI visuals, logo wallpaper, random
 off-system colors, or on-canvas taglines. One cover, one idea.
 
 Open items the team is still validating: the Eclipse cover direction on new product posts; Compute
-and Prisma Next have no dedicated color tokens yet (they inherit platform teal); and the skill
+and Prisma 8 have no dedicated color tokens yet (they inherit platform teal); and the skill
 depends on extracted Figma resources rather than a live source in every environment.

.claude/skills/content-create-hero-image/SKILL.md

@@ -29,7 +29,7 @@ Use [`README.md`](README.md) for usage and sample prompts; this `SKILL.md` is th
 - [`assets/tokens.json`](assets/tokens.json) — machine-readable tokens; the source of truth for hex/font values.
 - [`references/figma-source.md`](references/figma-source.md) — what `SOCIALS.fig` contains and how it was extracted.
 - [`references/figma-mcp.md`](references/figma-mcp.md) — **optional**: pull live specs/assets from the Prisma Figma workspace when a Figma MCP is connected.
-- [`assets/logos/`](assets/logos/) — official Prisma logo/symbol, Prisma Next mark + lockup, Postgres/Compute icons (`README.md`).
+- [`assets/logos/`](assets/logos/) — official Prisma logo/symbol, Prisma 8 mark + lockup, Postgres/Compute icons (`README.md`).
 - [`assets/fonts/`](assets/fonts/) — bundled brand fonts (Mona Sans, Inter, Geist Mono); used by the scripts.
 - [`assets/templates/cover.svg`](assets/templates/cover.svg) — parameterized starting template.
 - [`assets/examples/`](assets/examples/) — one worked hero/meta pair per house content module; the quality bar for new work.