feat(docs): add Prisma Compute docs section and integrate into the docs experience by ankur-arch · Pull Request #7931 · prisma/web

ankur-arch · 2026-06-03T10:10:48Z

Summary

Adds a new Prisma Compute docs section at /docs/compute and integrates it into the existing docs experience (top nav, sidenav, Getting Started, CLI and Console docs, quickstart callouts). Scope is limited to docs-owned files; no marketing, product, blog, or global website surfaces were touched.

Content is validated against three sources: the authoritative Compute product doc set, the prisma/prisma-cli repo (every command/flag), and the pdp-control-plane implementation (platform behavior and limits).

New pages

Compute section (/docs/compute)

index.mdx — overview with the resource model (workspace → project → branch → apps/databases)
getting-started.mdx — get started with the @prisma/cli beta (deploy loop, frameworks, project linking, production, CI/agents); sidebar label is @prisma/cli
branching.mdx — production/preview branches, CLI branch resolution, auto-creation, cleanup
deployments.mdx — deploy, local build/run, inspect, logs, promote, roll back, remove
database/connect-to-prisma-postgres.mdx — connect an app via DATABASE_URL
environment-variables.mdx — production/preview/branch scopes, write-only values, rules
domains.mdx — custom domains, CNAME setup, status lifecycle, retry, limits (3/app, production-only)
github.mdx — repo connection, deploy on push, branch event mapping, beta boundaries
faq.mdx — Q&A for people and agents
cli-reference.mdx — complete @prisma/cli reference: all command groups, flags, env vars, and error codes (cross-linked from /docs/cli and the getting-started page)
limitations.mdx — what the Public Beta does and doesn't do, in one place

Getting Started (/docs/prisma-compute/*)

deploy.mdx — deploy your first app (CLI path + hand-it-to-your-agent path with prompt template)
connect-to-prisma-postgres.mdx — quickstart for wiring an app to Prisma Postgres

Integration changes

Docs top nav: added Compute after Postgres (src/lib/layout.shared.tsx)
Root and Getting Started meta.json: new Compute entries
"Introduction to Prisma" and "Choose a setup path": Compute mentions
"Deploy to Compute" callouts on the five Prisma Postgres-backed quickstarts
CLI docs: note distinguishing the ORM prisma CLI from the @prisma/cli beta (prisma-cli binary)
Console docs: Compute in the product list; Concepts page extended with branches and Compute apps
Feature maturity page: new Public Beta level (what users can expect, what's stable, what can change before GA, caveats) plus a Compute-specific subsection
Badges: new beta badge type in the docs badge system; a single "Beta" chip on the Compute index instead of chips on every page (declutters the sidebar)
Sidebar coherence: short labels (@prisma/cli, Connect to Prisma Postgres, Domains); titles only, URLs unchanged
Positioning: the Compute intro carries the integrated platform story (model with Prisma ORM, store in Prisma Postgres, run on Compute; co-location keeps app-to-database latency low), per the product messaging guidance
Redirects: none needed — this PR only adds pages and changes titles; no public URL or anchor that previously shipped was removed (apps/docs/vercel.json is the place if that changes)

Validation

pnpm lint:links — 0 errors (561 files)
pnpm --filter docs types:check — passes
pnpm lint:spellcheck (cspell) — 0 issues across 681 files; added waitlist, dogfooding to cspell.json
Dev-server smoke test — all 12 Compute pages + updated pages return 200; nav, sidebar, Beta badge, callouts, and agent section render; no stray TODO output
Not from this PR: root pnpm types:check fails on main in @prisma/eclipse; local docs build needs MXBAI_API_KEY (search route)

Open product questions

Most earlier questions were resolved by the authoritative product docs (terminology is "app"; maturity is Public Beta; branches auto-create on deploy and are cleaned up via GitHub branch deletion; domains are CNAME-based, production-only, 3 per app). Still open:

Regions: Supported regions are not documented in any product source; the docs intentionally make no region claims. Confirm whether regions should be documented.
Runtime resource limits: Memory, CPU, request timeouts, and request body size are not documented; the Limitations page notes that exact limits and guardrails can change before GA.
Pricing and retention: Flagged on the maturity page as subject to change before GA; no pricing page exists for Compute yet.
Console create-service flow: The docs position the Console for inspection (per product docs). If the Console create-app flow should be documented, that needs UI copy review.
Next.js output: "standalone" requirement: Verified in the CLI repo skill but absent from the product doc set; kept as a note. Confirm it's still required.
GitHub App permission list: Not documented in any source; the docs describe the install flow without enumerating permissions.

Out of scope (handled separately)

Compute mentions on marketing/product pages, global site nav, and footer (apps/site, packages/ui) were deliberately not added.
The Console concepts diagram (/img/platform/pdp-concepts.png) still shows four concepts; it needs a refresh to include branches.

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation
- Added a full Prisma Compute docs section: overview, getting started, CLI reference, deployments, branching, domains, env vars, GitHub integration, FAQ, and limitations
- Added “Deploy to Compute” callouts across quickstarts and Console docs
- Updated docs navigation to surface Compute and added beta badges
New Features
- Interactive concept animations and code-step player added to improve documentation examples

…avigation Adds a new /docs/compute section (overview, @prisma/cli getting started, branching, Prisma Postgres connection, environment variables, custom domains, GitHub integration, FAQ/limitations), getting-started pages for deploying a first Compute service and connecting it to Prisma Postgres, and integrates Compute into the docs top nav, sidenav, Introduction, Choose a setup path, CLI and Console docs, plus "Deploy to Compute" callouts on the Prisma Postgres quickstarts. All CLI commands are sourced from prisma/prisma-cli, and platform behavior from pdp-control-plane. Open questions are left as non-rendering MDX TODO comments. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

vercel · 2026-06-03T10:10:55Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 8, 2026 1:58pm
docs	Ready	Preview, Comment	Jun 8, 2026 1:58pm
eclipse	Ready	Preview, Comment	Jun 8, 2026 1:58pm
site	Ready	Preview, Comment	Jun 8, 2026 1:58pm

github-actions · 2026-06-03T10:11:45Z

🍈 Lychee Link Check Report

196 links: ✅ 12 OK | 🚫 0 errors | 🔀 11 redirects | 👻 173 excluded

✅ All links are working!

Full Statistics Table

Status	Count
✅ Successful	12
🔀 Redirected	11
👻 Excluded	173
🚫 Errors	0
⛔ Unsupported	0
⏳ Timeouts	0
❓ Unknown	0

coderabbitai · 2026-06-03T10:11:59Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

Walkthrough

Adds a complete Prisma Compute docs section (overview, getting-started, deployments, branching, envs, domains, GitHub, CLI reference, FAQ, limitations), integrates Compute into navigation and index/getting-started pages, adds beta badge/frontmatter support, callouts in existing quickstarts, and new docs UI components for animated concept demos.

Changes

Prisma Compute documentation rollout

Layer / File(s)	Summary
Badge system for beta documentation status `apps/docs/source.config.ts`, `apps/docs/src/components/sidebar-badge-provider.tsx`, `apps/docs/src/lib/page-badges.ts`	Frontmatter schema, component types, and label/color mappings extended to support `"beta"` badge value.
Navigation and doc metadata structure `apps/docs/content/docs/(index)/meta.json`, `apps/docs/content/docs/meta.json`, `apps/docs/src/lib/layout.shared.tsx`, `apps/docs/content/docs/compute/meta.json`	Doc `meta.json` and sidebar links updated to include Compute; Getting Started activePaths extended for Compute routes.
Getting started and index entry points `apps/docs/content/docs/(index)/getting-started.mdx`, `apps/docs/content/docs/(index)/index.mdx`, `apps/docs/content/docs/(index)/prisma-compute/meta.json`	Index and Getting Started show a Deploy path and a Compute card linking to the first-app deploy guide.
Compute product overview and first deploy `apps/docs/content/docs/compute/index.mdx`	Compute overview page with Public Beta callout, resource model, and first-deploy CLI snippet.
Compute CLI getting started guide `apps/docs/content/docs/compute/getting-started.mdx`	Full CLI-based getting-started covering install, auth, deploy loop, framework flags, CI/service-token usage, and JSON envelope semantics.
Deploy your first Compute app quickstart `apps/docs/content/docs/(index)/prisma-compute/deploy.mdx`	Quickstart for deploying an app including auth, deploy, verify, logs, production redeploy example, and agent-assisted workflows.
Deployments and operational workflows `apps/docs/content/docs/compute/deployments.mdx`	Deployments page covering build/run, production promotion, inspect commands, logs, promote/rollback, and removal.
Branching model and branch management `apps/docs/content/docs/compute/branching.mdx`	Branching semantics, CLI selection precedence, creation, and cleanup behavior.
Environment variables, GitHub integration, and domains `apps/docs/content/docs/compute/environment-variables.mdx`, `apps/docs/content/docs/compute/github.mdx`, `apps/docs/content/docs/compute/domains.mdx`	Guides for env var scoping/CLI, GitHub connect/disconnect/webhook automation, and domain lifecycle including CLI commands and errors.
CLI reference and limitations `apps/docs/content/docs/compute/cli-reference.mdx`, `apps/docs/content/docs/compute/limitations.mdx`	Complete `@prisma/cli` reference and Public Beta limitations checklist.
Compute FAQ and common patterns `apps/docs/content/docs/compute/faq.mdx`	FAQ covering CLI usage, branches/apps/projects, env semantics, CI examples, common errors, domains, and beta scope.
Cross-linking from quickstart and CLI docs `apps/docs/content/docs/(index)/prisma-orm/quickstart/prisma-postgres.mdx`, `apps/docs/content/docs/(index)/prisma-postgres/quickstart/*`, `apps/docs/content/docs/console/...`, `apps/docs/content/docs/cli/index.mdx`	Callouts added to existing quickstarts, CLI overview, and Console docs linking to Compute.
Docs concept-animation UI `apps/docs/src/components/concept-animation/*`, `apps/docs/src/components/concept-animation/smooth-pre.tsx`, `apps/docs/src/mdx-components.tsx`	New ConceptAnimation/ConceptPlayer/presets/SmoothPre components and MDX mapping to render animated code-concept demos (uses CodeHike).
Package and build config `apps/docs/package.json`	Add `codehike` dependency and reorder devDependencies for tooling.
Dictionary updates `apps/docs/cspell.json`	Add `dogfooding` and `waitlist` to cspell words.
Bun regex tweak `apps/docs/source.config.ts`	Change bun replacement to global/multiline regex for multi-line strings.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and specifically describes the main change: adding a comprehensive Prisma Compute documentation section and integrating it throughout the docs experience.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

argos-ci · 2026-06-03T10:14:16Z

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	⚠️ Changes detected (Review)	1 changed	Jun 8, 2026, 2:04 PM

…maturity Validate and rework the Compute docs against the product doc set: - Adopt the product resource model (workspace → project → branch → apps/databases) and "app" terminology throughout - Standardize on `npx @prisma/cli@latest` invocation - Add Deployments and Limitations pages; resolve all prior TODOs (branch auto-creation, cleanup via GitHub, domain limits, error codes) - Document Public Beta on the feature-maturity page and link it from Compute pages; replace "early access" framing - Add a `beta` badge type and keep a single sidebar chip on the Compute index to reduce clutter - Add an agent-driven deploy path to the deploy quickstart - Add branch and Compute app concepts to Console concepts - Add waitlist/dogfooding to cspell.json; spellcheck, links, and types pass Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (1)

apps/docs/src/lib/page-badges.ts (1)
3-3: ⚡ Quick win

Three parallel definitions of the badge set are quietly drifting waiting to happen.

The same allowed-values list now lives in three places: the zod badge enum in source.config.ts, BadgeType in sidebar-badge-provider.tsx, and this BadgeType. You kept all three in sync for "beta" — but nothing forces that. The trap is the as BadgeType cast on page.data.badge: if someone later adds a value to the zod schema only, the cast happily accepts it at runtime while BADGE_LABEL/BADGE_COLOR lookups return undefined, so the badge silently fails to render with no type error to catch it.

A cheap, durable fix is to define BadgeType once and import it in the other module (type-only imports from a "use client" file are erased at build, so there's no client/server hazard):
♻️ Consolidate to a single source
-export type BadgeType = "early-access" | "beta" | "deprecated" | "preview";
+import type { BadgeType } from "`@/components/sidebar-badge-provider`";
+export type { BadgeType };
Even better long-term: derive the TS type from the zod enum (z.infer) so the schema is the single source of truth — though that's a larger change you can defer.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/docs/src/lib/page-badges.ts` at line 3, The BadgeType union is
duplicated across modules causing silent runtime mismatches; fix by defining
BadgeType in one place (preferably next to the zod `badge` enum in
source.config.ts) and change other files (apps/docs/src/lib/page-badges.ts and
sidebar-badge-provider.tsx) to import that single exported type via a type-only
import, then remove the local BadgeType declarations so lookups like BADGE_LABEL
and BADGE_COLOR and casts of page.data.badge all use the same canonical type;
optionally, later derive the TS type from the zod enum with z.infer for a single
source-of-truth.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/docs/content/docs/compute/domains.mdx`:
- Around line 33-37: Verify that the example command `npx `@prisma/cli`@latest app
domain wait` is actually supported by the latest Prisma CLI and that its
subcommand name is correct (search `@prisma/cli@latest --help` or the CLI source
for `app domain wait`); if the command is unsupported, replace the example with
a supported command or remove it. If the command exists, confirm the exact
semantics of the `--timeout` flag (especially `--timeout 0`) and update the text
to state precisely whether `0` means “perform a single status check and exit” or
“wait indefinitely/no timeout,” referencing `app domain wait` and `--timeout 0`
in the updated copy so readers are not misled.

---

Nitpick comments:
In `@apps/docs/src/lib/page-badges.ts`:
- Line 3: The BadgeType union is duplicated across modules causing silent
runtime mismatches; fix by defining BadgeType in one place (preferably next to
the zod `badge` enum in source.config.ts) and change other files
(apps/docs/src/lib/page-badges.ts and sidebar-badge-provider.tsx) to import that
single exported type via a type-only import, then remove the local BadgeType
declarations so lookups like BADGE_LABEL and BADGE_COLOR and casts of
page.data.badge all use the same canonical type; optionally, later derive the TS
type from the zod enum with z.infer for a single source-of-truth.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: cf3ee908-f9cc-4b99-b172-ba53906dccc8

📥 Commits

Reviewing files that changed from the base of the PR and between f0f3afb and 2b8c66c.

📒 Files selected for processing (27)

apps/docs/content/docs/(index)/getting-started.mdx
apps/docs/content/docs/(index)/index.mdx
apps/docs/content/docs/(index)/prisma-compute/connect-to-prisma-postgres.mdx
apps/docs/content/docs/(index)/prisma-compute/deploy.mdx
apps/docs/content/docs/(index)/prisma-orm/quickstart/prisma-postgres.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/drizzle-orm.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/kysely.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/prisma-orm.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/typeorm.mdx
apps/docs/content/docs/compute/branching.mdx
apps/docs/content/docs/compute/database/connect-to-prisma-postgres.mdx
apps/docs/content/docs/compute/deployments.mdx
apps/docs/content/docs/compute/domains.mdx
apps/docs/content/docs/compute/environment-variables.mdx
apps/docs/content/docs/compute/faq.mdx
apps/docs/content/docs/compute/getting-started.mdx
apps/docs/content/docs/compute/github.mdx
apps/docs/content/docs/compute/index.mdx
apps/docs/content/docs/compute/limitations.mdx
apps/docs/content/docs/compute/meta.json
apps/docs/content/docs/console/concepts.mdx
apps/docs/content/docs/console/index.mdx
apps/docs/content/docs/console/more/feature-maturity.mdx
apps/docs/cspell.json
apps/docs/source.config.ts
apps/docs/src/components/sidebar-badge-provider.tsx
apps/docs/src/lib/page-badges.ts

✅ Files skipped from review due to trivial changes (14)

apps/docs/cspell.json
apps/docs/content/docs/(index)/prisma-postgres/quickstart/kysely.mdx
apps/docs/content/docs/compute/limitations.mdx
apps/docs/content/docs/compute/deployments.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/drizzle-orm.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/typeorm.mdx
apps/docs/content/docs/(index)/prisma-compute/connect-to-prisma-postgres.mdx
apps/docs/content/docs/compute/getting-started.mdx
apps/docs/content/docs/compute/branching.mdx
apps/docs/content/docs/compute/meta.json
apps/docs/content/docs/compute/github.mdx
apps/docs/content/docs/compute/database/connect-to-prisma-postgres.mdx
apps/docs/content/docs/compute/faq.mdx
apps/docs/content/docs/compute/environment-variables.mdx

🚧 Files skipped from review as they are similar to previous changes (5)

apps/docs/content/docs/(index)/index.mdx
apps/docs/content/docs/console/index.mdx
apps/docs/content/docs/(index)/prisma-compute/deploy.mdx
apps/docs/content/docs/compute/index.mdx
apps/docs/content/docs/(index)/prisma-postgres/quickstart/prisma-orm.mdx

- New /compute/cli-reference page covering all command groups, flags, environment variables, and error codes; cross-linked from /cli and /compute/getting-started - Sidebar titles: "@prisma/cli", "Connect to Prisma Postgres", "Domains" for shorter, coherent labels (URLs unchanged, so no redirects needed) - Align the Compute intro with the integrated platform story (ORM + Postgres + Compute, co-location for low latency) - Prose style pass: prefer flowing sentences over choppy fragments Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…r clarity - Remove --prod flag (no longer exists); document production deploys via branch targeting plus confirmation, with CONFIRMATION_REQUIRED in non-interactive mode - Replace PROD_DEPLOY_REQUIRES_FLAG with CONFIRMATION_REQUIRED - Add --trace global flag, JSON envelope docs, expanded error-code tables - Remove Connect to Prisma Postgres pages; fold content into environment-variables and repoint all links - Add explicit sign-in step to getting-started paths - Rewrite all pages: lower jargon, answer-first sections, clearer CTAs, no em dashes - Landing page: Compute and Postgres as primary cards; getting-started gains equivalent Compute steps Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Add ConceptAnimation MDX component: Code Hike token transitions over word-level tokens, autoplay with in-view/hover/reduced-motion handling, and grid-stacked sizers so steps never shift layout - Use it for the resource model (index, branching, faq), the GitHub connection levels (github), and env var resolution (environment-variables) - Fix multi-line bun x -> bunx --bun conversion in source.config.ts - Give bare assertions their reasons across all compute pages (--json, promote rebuilds, rollback reuse, write-only env values, error codes) - Rename Limitations to Known limitations and trim filler phrases Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Add the public-beta launch post for Monday 2026-06-08, adapting the announcement copy in the blog's voice. The "Try it" section uses the codehike-powered AgentPrompt to play a real `@prisma/cli@latest app deploy --db` run: the prompt is typed, then captured deploy logs stream in line by line. Terminal height is reserved up front so there is no layout shift. Env var names only, no credentials. Also refresh Shane Neubauer's author avatar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Replace the ASCII token-morph animations with animated box-and-arrow SVG flows that match the resource model: Project -> Branch -> Infrastructure (Variables/App/DB), variable scope resolution (production/preview/branch override), and GitHub push-to-deploy. - Extract the player chrome (progress bar, stepper, autoplay, reduced motion) into a shared PlayerShell used by both renderers. - Add flow.tsx + flow-presets.ts: theme-aware color-coded boxes, rounded orthogonal connectors with arrowheads, per-step draw-in and emphasis. - ConceptAnimation dispatches names with a scene to the flow renderer and falls back to the Code Hike animation otherwise, so MDX is unchanged. Fixed SVG viewBox + grid-stacked captions keep the layout from shifting as you step through. compute-model, env-layers, and github-connection all render as flows. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The env animation only hinted at scope in the branch sub-text. Rebuild it as a composition diagram: scopes you set on the left (production, preview, branch override) resolve into the actual variable set each branch deploys with on the right, every row color-coded by the scope it came from, with a legend. Steps now isolate the surprising default: production resolves to production only; every preview branch automatically inherits the shared preview set; a branch override then layers on key by key (replacing DATABASE_URL, adding FEATURE_FLAG) while the rest still flow through. Adds row rendering, per-step row overrides, a legend, fanned-out edges, and production/resolved box variants to the flow renderer. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

- Render scope-box subtitles on their own line so "Branch override / --branch feature/search" no longer overflows the box. - Env flow now contrasts the default with the override: a second preview branch (bug/fix-issue) with no override stays on the plain preview set while feature/search composes its override on top, making the inherit-preview-by-default behaviour explicit. - Reflect the same nuance in the model flow: the Variables chip carries its scope (production vs preview) and the captions note that variables follow a scope while App and DB are isolated per branch. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Reconcile the flow animations with the compute docs prose so they reinforce, not contradict, the documented model: - Overview intro no longer promises the model animation "ships to production"; it describes the resource model and variable scoping the animation actually shows. - GitHub flow now reflects the documented two levels (workspace owns the GitHub App installation; each project points at one repository) and drops the claim that merging to main auto-deploys to production. Per the deploy docs, GitHub events build the pushed commit and deploy the matching branch; production promotion stays deliberate. - Model captions use the docs' "scoped to preview" framing instead of "private copy", so variable scoping reads consistently with the environment-variables and branching pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Join the friction sentence into one line and format the @prisma handle as code in the feedback line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Add a per-edge bendX override so the env diagram's parallel dashed edges (preview and override into the same resolved box) route in distinct vertical lanes instead of overlapping. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

vercel Bot deployed to Preview – eclipse June 3, 2026 10:11 View deployment

vercel Bot deployed to Preview – blog June 3, 2026 10:11 View deployment

vercel Bot deployed to Preview – site June 3, 2026 10:12 View deployment

vercel Bot deployed to Preview – docs June 3, 2026 10:13 View deployment

vercel Bot deployed to Preview – eclipse June 3, 2026 10:42 View deployment

vercel Bot deployed to Preview – blog June 3, 2026 10:42 View deployment

vercel Bot deployed to Preview – site June 3, 2026 10:42 View deployment

vercel Bot deployed to Preview – docs June 3, 2026 10:43 View deployment

coderabbitai Bot reviewed Jun 3, 2026

View reviewed changes

Comment thread apps/docs/content/docs/compute/domains.mdx

vercel Bot deployed to Preview – blog June 3, 2026 10:58 View deployment

vercel Bot deployed to Preview – eclipse June 3, 2026 10:58 View deployment

vercel Bot deployed to Preview – site June 3, 2026 10:58 View deployment

vercel Bot deployed to Preview – docs June 3, 2026 10:59 View deployment

ankur-arch self-assigned this Jun 3, 2026

vercel Bot deployed to Preview – eclipse June 3, 2026 15:11 View deployment

vercel Bot deployed to Preview – blog June 3, 2026 15:11 View deployment

vercel Bot deployed to Preview – site June 3, 2026 15:11 View deployment

vercel Bot deployed to Preview – docs June 3, 2026 15:13 View deployment

vercel Bot deployed to Preview – blog June 4, 2026 00:08 View deployment

vercel Bot deployed to Preview – eclipse June 4, 2026 00:08 View deployment

vercel Bot deployed to Preview – site June 4, 2026 00:08 View deployment

Merge remote-tracking branch 'origin/main' into compute-docs

c8ced78

vercel Bot deployed to Preview – eclipse June 5, 2026 09:52 View deployment

vercel Bot deployed to Preview – blog June 5, 2026 09:52 View deployment

vercel Bot deployed to Preview – site June 5, 2026 09:52 View deployment

vercel Bot deployed to Preview – docs June 5, 2026 09:54 View deployment

vercel Bot deployed to Preview – eclipse June 5, 2026 12:32 View deployment

vercel Bot deployed to Preview – blog June 5, 2026 12:32 View deployment

vercel Bot deployed to Preview – site June 5, 2026 12:32 View deployment

vercel Bot deployed to Preview – docs June 5, 2026 12:33 View deployment

vercel Bot deployed to Preview – eclipse June 8, 2026 09:59 View deployment

vercel Bot deployed to Preview – blog June 8, 2026 09:59 View deployment

vercel Bot deployed to Preview – site June 8, 2026 09:59 View deployment

vercel Bot deployed to Preview – docs June 8, 2026 10:00 View deployment

vercel Bot deployed to Preview – eclipse June 8, 2026 11:04 View deployment

vercel Bot deployed to Preview – blog June 8, 2026 11:04 View deployment

vercel Bot deployed to Preview – site June 8, 2026 11:05 View deployment

vercel Bot deployed to Preview – docs June 8, 2026 11:05 View deployment

vercel Bot deployed to Preview – eclipse June 8, 2026 11:15 View deployment

vercel Bot deployed to Preview – blog June 8, 2026 11:15 View deployment

vercel Bot deployed to Preview – site June 8, 2026 11:15 View deployment

vercel Bot deployed to Preview – docs June 8, 2026 11:17 View deployment

vercel Bot deployed to Preview – eclipse June 8, 2026 12:50 View deployment

vercel Bot deployed to Preview – blog June 8, 2026 12:50 View deployment

ankur-arch and others added 2 commits June 8, 2026 15:39

docs(blog): tweak compute launch post copy

d91e116

Join the friction sentence into one line and format the @prisma handle as code in the feedback line. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(docs): add Prisma Compute docs section and integrate into the docs experience#7931

feat(docs): add Prisma Compute docs section and integrate into the docs experience#7931
ankur-arch wants to merge 21 commits into
mainfrom
compute-docs

ankur-arch commented Jun 3, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

vercel Bot commented Jun 3, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 3, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Jun 3, 2026 •

edited

Loading

Reviews paused

❌ Failed checks (1 warning)

Uh oh!

argos-ci Bot commented Jun 3, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

ankur-arch commented Jun 3, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

New pages

Integration changes

Validation

Open product questions

Out of scope (handled separately)

Summary by CodeRabbit

Uh oh!

vercel Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🍈 Lychee Link Check Report

✅ All links are working!

Uh oh!

coderabbitai Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Estimated code review effort

❌ Failed checks (1 warning)

Uh oh!

argos-ci Bot commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

ankur-arch commented Jun 3, 2026 •

edited by coderabbitai Bot

Loading

vercel Bot commented Jun 3, 2026 •

edited

Loading

github-actions Bot commented Jun 3, 2026 •

edited

Loading

coderabbitai Bot commented Jun 3, 2026 •

edited

Loading

argos-ci Bot commented Jun 3, 2026 •

edited

Loading