docs: add Prisma Next getting started guides#7933
Open
AmanVarshney01 wants to merge 9 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Note Reviews pausedIt 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 Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThis PR reorganizes Prisma Next docs: adds Prisma Postgres quickstarts and import guides, creates a /next/getting-started hub and a "What is Prisma Next?" page, harmonizes add-to-existing instructions, updates redirects/version mappings, and adjusts banner styling and sidebar badge behavior. ChangesPrisma Next Documentation Hub Restructuring
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Contributor
🍈 Lychee Link Check Report61 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
ankur-arch
reviewed
Jun 4, 2026
ankur-arch
reviewed
Jun 4, 2026
ankur-arch
reviewed
Jun 4, 2026
Contributor
|
@AmanVarshney01 The versioning dropdown currently lets users switch to the Prisma Next docs, which is great. Could we also make Prisma Next more prominent in the latest docs? Since Prisma Next will become the next major version, it would be useful to add a clear callout encouraging users to try it out and share feedback. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
apps/docs/src/lib/version.ts (1)
43-57:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd reverse mapping for
/next/prisma-postgresto preserve version-switch context.When switching from Next → Latest on Line 43-57,
/next/prisma-postgresis currently unmapped, so fallback sends users to/instead of/prisma-postgres. This loses section context in the version switch flow.Suggested patch
const LATEST_GETTING_STARTED_PATHS_BY_NEXT_PATH = new Map<string, string>([ [NEXT_GETTING_STARTED_ROOT, "/"], ["/next/getting-started", "/getting-started"], ["/next/what-is-prisma-next", "/prisma-orm"], + ["/next/prisma-postgres", "/prisma-postgres"], ["/next/prisma-postgres/quickstart/prisma-next", "/prisma-postgres/quickstart/prisma-orm"], [ "/next/prisma-postgres/import-from-existing-database-postgresql", "/prisma-postgres/import-from-existing-database-postgresql", ],🤖 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/version.ts` around lines 43 - 57, The map LATEST_GETTING_STARTED_PATHS_BY_NEXT_PATH is missing a reverse entry for the "/next/prisma-postgres" section causing the version switch to fall back to "/" and lose context; add an entry mapping "/next/prisma-postgres" to "/prisma-postgres" alongside the other entries (update the LATEST_GETTING_STARTED_PATHS_BY_NEXT_PATH constant near NEXT_GETTING_STARTED_ROOT) so switching from Next → Latest preserves the prisma-postgres section context.
🤖 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.
Outside diff comments:
In `@apps/docs/src/lib/version.ts`:
- Around line 43-57: The map LATEST_GETTING_STARTED_PATHS_BY_NEXT_PATH is
missing a reverse entry for the "/next/prisma-postgres" section causing the
version switch to fall back to "/" and lose context; add an entry mapping
"/next/prisma-postgres" to "/prisma-postgres" alongside the other entries
(update the LATEST_GETTING_STARTED_PATHS_BY_NEXT_PATH constant near
NEXT_GETTING_STARTED_ROOT) so switching from Next → Latest preserves the
prisma-postgres section context.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 0d5cc393-df31-46a4-8adc-7b639e51bfed
📒 Files selected for processing (31)
apps/docs/content/docs/(index)/next/add-to-existing-project/meta.jsonapps/docs/content/docs/(index)/next/add-to-existing-project/mongodb.mdxapps/docs/content/docs/(index)/next/add-to-existing-project/postgresql.mdxapps/docs/content/docs/(index)/next/getting-started.mdxapps/docs/content/docs/(index)/next/index.mdxapps/docs/content/docs/(index)/next/meta.jsonapps/docs/content/docs/(index)/next/prisma-postgres/from-the-cli.mdxapps/docs/content/docs/(index)/next/prisma-postgres/import-from-existing-database-mysql.mdxapps/docs/content/docs/(index)/next/prisma-postgres/import-from-existing-database-postgresql.mdxapps/docs/content/docs/(index)/next/prisma-postgres/quickstart/prisma-next.mdxapps/docs/content/docs/(index)/next/what-is-prisma-next.mdxapps/docs/content/docs/cli/next/index.mdxapps/docs/content/docs/cli/next/init.mdxapps/docs/content/docs/orm/next/concepts/contract-first-design.mdxapps/docs/content/docs/orm/next/concepts/extension-packs.mdxapps/docs/content/docs/orm/next/concepts/meta.jsonapps/docs/content/docs/orm/next/concepts/query-apis.mdxapps/docs/content/docs/orm/next/concepts/schema-definition-and-contract-emission.mdxapps/docs/content/docs/orm/next/extensions/cipherstash.mdxapps/docs/content/docs/orm/next/extensions/meta.jsonapps/docs/content/docs/orm/next/extensions/pgvector.mdxapps/docs/content/docs/orm/next/extensions/postgis.mdxapps/docs/content/docs/orm/next/guides/building-queries-with-sql-dsl.mdxapps/docs/content/docs/orm/next/guides/deploying-to-serverless-runtimes.mdxapps/docs/content/docs/orm/next/guides/error-handling-patterns.mdxapps/docs/content/docs/orm/next/guides/managing-database-migrations.mdxapps/docs/content/docs/orm/next/guides/meta.jsonapps/docs/content/docs/orm/next/guides/using-the-orm-client.mdxapps/docs/content/docs/orm/next/index.mdxapps/docs/content/docs/orm/next/meta.jsonapps/docs/src/lib/version.ts
💤 Files with no reviewable changes (18)
- apps/docs/content/docs/orm/next/guides/error-handling-patterns.mdx
- apps/docs/content/docs/orm/next/guides/managing-database-migrations.mdx
- apps/docs/content/docs/orm/next/guides/using-the-orm-client.mdx
- apps/docs/content/docs/orm/next/concepts/meta.json
- apps/docs/content/docs/orm/next/guides/deploying-to-serverless-runtimes.mdx
- apps/docs/content/docs/orm/next/extensions/meta.json
- apps/docs/content/docs/orm/next/concepts/query-apis.mdx
- apps/docs/content/docs/orm/next/guides/meta.json
- apps/docs/content/docs/(index)/next/add-to-existing-project/meta.json
- apps/docs/content/docs/orm/next/concepts/contract-first-design.mdx
- apps/docs/content/docs/orm/next/concepts/schema-definition-and-contract-emission.mdx
- apps/docs/content/docs/orm/next/concepts/extension-packs.mdx
- apps/docs/content/docs/orm/next/extensions/cipherstash.mdx
- apps/docs/content/docs/orm/next/extensions/pgvector.mdx
- apps/docs/content/docs/orm/next/extensions/postgis.mdx
- apps/docs/content/docs/orm/next/guides/building-queries-with-sql-dsl.mdx
- apps/docs/content/docs/(index)/next/add-to-existing-project/postgresql.mdx
- apps/docs/content/docs/(index)/next/add-to-existing-project/mongodb.mdx
✅ Files skipped from review due to trivial changes (8)
- apps/docs/content/docs/cli/next/init.mdx
- apps/docs/content/docs/orm/next/meta.json
- apps/docs/content/docs/(index)/next/what-is-prisma-next.mdx
- apps/docs/content/docs/(index)/next/prisma-postgres/from-the-cli.mdx
- apps/docs/content/docs/(index)/next/prisma-postgres/quickstart/prisma-next.mdx
- apps/docs/content/docs/(index)/next/prisma-postgres/import-from-existing-database-mysql.mdx
- apps/docs/content/docs/(index)/next/getting-started.mdx
- apps/docs/content/docs/(index)/next/prisma-postgres/import-from-existing-database-postgresql.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- apps/docs/content/docs/orm/next/index.mdx
- apps/docs/content/docs/(index)/next/meta.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
create-prisma@next.npx prisma-next initand redirects the old create-prisma page back to Getting Started.Validation
pnpm --filter docs run lint:spellcheckpnpm --filter docs run lint:linkspnpm --filter docs run types:check/docs/next, quickstart pages, existing-project pages, and redirects.Summary by CodeRabbit
Documentation
Style
Chore