docs: align getting-started and overview entry points with Compute

Reorganize the getting-started page around what you want to do first
(deploy, start a new project, add to an existing project), refresh the
landing page copy and cards, and tighten the Compute overview model
description.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: ankur-arch

apps/docs/content/docs/(index)/getting-started.mdx

@@ -1,30 +1,35 @@
 ---
 title: Choose a setup path
-description: Choose the fastest path to start using Prisma ORM or Prisma Postgres in a new or existing project.
+description: Choose the fastest path to start using Prisma ORM, Prisma Postgres, or Prisma Compute in a new or existing TypeScript project.
 url: /getting-started
 metaTitle: Prisma getting started
-metaDescription: Choose a Prisma quickstart for new or existing projects and get from schema to first query quickly.
+metaDescription: Choose the fastest path to start using Prisma ORM, Prisma Postgres, or Prisma Compute in a new or existing TypeScript project.
 ---
 
-Prisma gives you a few good starting points depending on whether you need a database, already have one, want the smallest possible local setup, or are ready to deploy your app.
+Prisma gives you a few starting points depending on what you want to do first: deploy an app, create a database, use Prisma ORM locally, or add Prisma to an existing project.
 
 ## Choose your path
 
+### Deploy a full-stack app with a database
+
+Use this path if you want to deploy a TypeScript app with Prisma Compute and run it alongside Prisma Postgres.
+
+- [Deploy your first app](/prisma-compute/deploy) on [Prisma Compute](/compute), currently in Public Beta, to run it next to your Prisma Postgres database
+
 ### Start a new project
 
+Use this path if you are creating a new app and want to set up Prisma from the beginning.
+
 - [Quickstart with Prisma Postgres](/prisma-orm/quickstart/prisma-postgres) for the fastest end-to-end path with a managed PostgreSQL database
 - [Quickstart with PostgreSQL](/prisma-orm/quickstart/postgresql) if you want to work with PostgreSQL
 - [Quickstart with SQLite](/prisma-orm/quickstart/sqlite) for a lightweight local setup
 - [Quickstart with MySQL](/prisma-orm/quickstart/mysql) if your application uses MySQL
 - [Quickstart with MongoDB](/prisma-orm/quickstart/mongodb) if your application uses MongoDB
 
-### Deploy your app
-
-- [Deploy your first app](/prisma-compute/deploy) on [Prisma Compute](/compute), currently in Public Beta, to run it next to your Prisma Postgres database
-- [Set environment variables](/compute/environment-variables) to connect your deployed app to a database
-
 ### Add Prisma to an existing project
 
+Use this path if you already have an application or database and want to add Prisma ORM.
+
 - [Add Prisma ORM to an existing PostgreSQL project](/prisma-orm/add-to-existing-project/postgresql)
 - [Add Prisma ORM to an existing MySQL project](/prisma-orm/add-to-existing-project/mysql)
 - [Add Prisma ORM to an existing SQLite project](/prisma-orm/add-to-existing-project/sqlite)
@@ -33,19 +38,22 @@ Prisma gives you a few good starting points depending on whether you need a data
 
 ## What you will do
 
-No matter which guide you choose, the flow is usually the same:
+Most Prisma ORM and Prisma Postgres guides follow the same basic flow:
 
 1. Define a database connection and data model in your [Prisma schema](/orm/prisma-schema/overview).
-2. Install Prisma CLI and [Prisma Client](/orm/prisma-client).
-3. Run `prisma generate` to create a type-safe client for your schema.
-4. Create or introspect your database, then start sending queries from your application.
+2. Set up your database, either with [Prisma Postgres](/postgres) or another supported database.
+3. Install Prisma CLI and [Prisma Client](/orm/prisma-client).
+4. Run `prisma generate` to create a type-safe client for your schema.
+5. Create or introspect your database.
+6. Start sending queries from your application.
 
-If you're deploying to [Prisma Compute](/compute), the equivalent flow is:
+Then you can deploy your app to [Prisma Compute](/compute). The flow is:
 
 1. Sign in with `npx @prisma/cli@latest auth login`.
 2. Run `npx @prisma/cli@latest app deploy` from your app directory to get a live URL.
-3. Set your database connection string and other config as [environment variables](/compute/environment-variables).
-4. Redeploy to apply them, then keep shipping from the CLI or [connect GitHub](/compute/github) to deploy on push.
+3. Connect your app to [Prisma Postgres](/postgres) or another database with [environment variables](/compute/environment-variables).
+4. Redeploy to apply the environment variables.
+5. Keep deploying from the CLI, or [connect GitHub](/compute/github) to deploy on push.
 
 ## Next steps
 

apps/docs/content/docs/(index)/index.mdx

@@ -1,37 +1,60 @@
 ---
 title: Introduction to Prisma
-description: Build data-driven applications with ease using Prisma ORM and Prisma Postgres
+description: Build, deploy, and iterate on TypeScript applications with Prisma ORM, Prisma Postgres, and Prisma Compute.
 url: /
 metaTitle: Get started with Prisma
-metaDescription: 'Build data-driven applications with ease using Prisma ORM, add connection pooling with Prisma Postgres.'
+metaDescription: "Build, deploy, and iterate on TypeScript applications with Prisma ORM, Prisma Postgres, and Prisma Compute."
 ---
+
 [**Prisma ORM**](/orm) is an open-source ORM that provides fast, type-safe access to Postgres, MySQL, SQLite, and other databases, and runs smoothly across Node.js, Bun, and Deno.
 
 ```npm
-npx prisma init
+npx prisma@latest init
 ```
 
-
 [**Prisma Postgres**](/postgres) is a fully managed PostgreSQL database that scales to zero, integrates with [Prisma ORM](/orm) and [Prisma Studio](/studio), and includes a [generous free tier](https://www.prisma.io/pricing).
 
 ```npm
-npx create-db
+npx create-db@latest
 ```
 
-
-[**Prisma Compute**](/compute) runs your app next to your Prisma Postgres database, currently in [Public Beta](/console/more/feature-maturity#public-beta). Deploy Next.js, Hono, TanStack Start, and Bun apps, with an isolated preview for every branch.
+[**Prisma Compute**](/compute) is TypeScript app hosting for running your app next to your Prisma Postgres database. It is currently in [Public Beta](/console/more/feature-maturity#public-beta). Deploy Next.js, Hono, TanStack Start, and Bun apps, with an isolated preview for every branch.
 
 ```npm
 npx @prisma/cli@latest app deploy
 ```
 
-
 <Cards>
-  <Card href="/prisma-compute/deploy" title="Use Prisma Compute" icon={<Rocket className="text-primary" />}>
-    **Ready to deploy?** Run your app next to your database, with a live preview for every branch.
+  <Card
+    href="/prisma-compute/deploy"
+    title="Use Prisma Compute"
+    icon={<Rocket className="text-primary" />}
+  >
+    Deploy and run your TypeScript app next to your database, with a live
+    preview for every branch.
   </Card>
-  <Card href="/prisma-orm/quickstart/prisma-postgres" title="Use Prisma Postgres" icon={<div className="text-primary"><svg aria-hidden="true" xmlns="http://www.w3.org/2000/svg" width="159" height="195" viewBox="0 0 640 640" fill="none"><path d="M355.2 85C348.2 72.1 334.7 64 320 64C305.3 64 291.8 72.1 284.8 85L209.7 224L430.2 224L355.1 85zM123.3 384L516.6 384L456.1 272L183.7 272L123.2 384zM97.4 432L68.8 485C62.1 497.4 62.4 512.4 69.6 524.5C76.8 536.6 89.9 544 104 544L536 544C550.1 544 563.1 536.6 570.4 524.5C577.7 512.4 577.9 497.4 571.2 485L542.6 432L97.4 432z" fill="currentColor"/></svg></div>
-}>
-    **Need a database?** Get started with your favorite framework and Prisma Postgres.
+  <Card
+    href="/prisma-orm/quickstart/prisma-postgres"
+    title="Use Prisma Postgres"
+    icon={
+      <div className="text-primary">
+        <svg
+          aria-hidden="true"
+          xmlns="http://www.w3.org/2000/svg"
+          width="159"
+          height="195"
+          viewBox="0 0 640 640"
+          fill="none"
+        >
+          <path
+            d="M355.2 85C348.2 72.1 334.7 64 320 64C305.3 64 291.8 72.1 284.8 85L209.7 224L430.2 224L355.1 85zM123.3 384L516.6 384L456.1 272L183.7 272L123.2 384zM97.4 432L68.8 485C62.1 497.4 62.4 512.4 69.6 524.5C76.8 536.6 89.9 544 104 544L536 544C550.1 544 563.1 536.6 570.4 524.5C577.7 512.4 577.9 497.4 571.2 485L542.6 432L97.4 432z"
+            fill="currentColor"
+          />
+        </svg>
+      </div>
+    }
+  >
+    Get started with your favorite framework and Prisma Postgres as the
+    database.
   </Card>
 </Cards>

apps/docs/content/docs/compute/index.mdx

@@ -1,13 +1,13 @@
 ---
 title: Prisma Compute
-description: "Deploy and run your TypeScript app on the same platform as Prisma Postgres, with your schema, database, hosting, and previews managed together."
+description: "Deploy TypeScript apps alongside Prisma Postgres, with hosting, database branches, and previews managed together."
 url: /compute
 badge: beta
-metaTitle: Overview | Prisma Compute
-metaDescription: Learn what Prisma Compute is, how it runs your app alongside Prisma Postgres, and how to deploy your first app.
+metaTitle: Prisma Compute | TypeScript app hosting for Prisma Postgres
+metaDescription: Learn how Prisma Compute deploys TypeScript apps alongside Prisma Postgres, with isolated branch previews, database branches, and CLI-first workflows.
 ---
 
-Prisma Compute deploys and runs your TypeScript app on the same platform as [Prisma Postgres](/postgres). You model your data with [Prisma ORM](/orm), store it in Prisma Postgres, and deploy your app to Prisma Compute, so your schema, database, and hosting are managed together in one sandbox.
+Prisma Compute is TypeScript app hosting built to run alongside [Prisma Postgres](/postgres). You model your data with [Prisma ORM](/orm), store it in Prisma Postgres, and deploy your app with Prisma Compute, so your schema, database, hosting, and branch previews work together in one Prisma project.
 
 :::info[Public Beta]
 
@@ -17,25 +17,25 @@ Prisma Compute is in [Public Beta](/console/more/feature-maturity#public-beta) a
 
 ## Get started
 
-The best way to understand Compute is to deploy an app. The quickstart gets a TypeScript app to a live URL in a few minutes, then connects GitHub so every push deploys automatically.
+The best way to understand Compute is to deploy an app. The quickstart takes a TypeScript app to a live URL in a few minutes, then connects GitHub so every push can deploy automatically.
 
 <Cards>
   <Card href="/prisma-compute/deploy" title="Deploy your first app">
     The quickstart: sign in, deploy, verify, and connect GitHub.
   </Card>
 </Cards>
 
-To learn how Compute works, [the model](#the-model) below shows how each branch gets an isolated copy of your app and database, so previews never touch production.
+To learn how Compute works, [the model](#the-model) below shows how each branch gets isolated app and database resources, so preview work never touches production.
 
 ## The model
 
 Compute organizes everything into a few resources:
 
 - A **project** groups one product or codebase.
-- A **branch** maps to a Git branch in the linked repository, and gets its own isolated app and deployments.
+- A **branch** maps to a Git branch in the linked repository, and gets its own isolated app, environment variables, and deployments.
 - An **app** is an HTTP service, such as a frontend or backend, and can have multiple **deployments**.
 
-The branch is the idea that ties Compute together, because each branch owns its own app, database, and URL. When you create a branch, Compute provisions a full copy of that infrastructure, so preview work runs in complete isolation and never touches production.
+The branch is the concept that ties Compute together. Each branch owns its own app, database, URL, and environment variables. When you create a branch, Compute provisions isolated resources for that branch, so you can test changes in preview without affecting production.
 
 - **Production**: the default Git branch (e.g., `main`) is your production branch, with its own resources and environment variables.
 - **Preview**: every other branch is a preview branch, with its own isolated resources and environment variables scoped to **preview**.