feat: add Prisma Next#7893
Draft
ankur-arch wants to merge 4 commits into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Contributor
🍈 Lychee Link Check Report17 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎ Awaiting the start of a new Argos build… |
* docs: add Prisma Next getting started guides * docs: address Prisma Next getting started feedback * docs: add Prisma Next getting started section * docs: refine Prisma Next quickstart steps * docs: streamline Prisma Next prerequisites * docs: simplify Prisma Next ORM pages * docs: trim Prisma Next overview * docs: restore Prisma Next getting started pages * docs: preselect Prisma Next database guides * Added Prisma Next docs in ORM section * docs: reframe Prisma Next as Early Access and default docs entry to Next - Replace "not production ready" callouts with Early Access notes across the Prisma Next docs pages, the Prisma Next blog series, and the ORM / Console feature-maturity definitions. New messaging: Prisma Next is the next major version of Prisma ORM, in Early Access, expect changes, share feedback; Prisma 7 is GA, keep using it for production. - Point the site nav "Docs" link to /docs/next and the nav + footer "ORM" links to /docs/orm/next so users land on Prisma Next. - Rename the ORM Next intro sidebar entry from "What is Prisma Next?" to "Prisma Next" for parity with the Prisma ORM (Latest) docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: use finalized Early Access callout copy for Prisma Next Apply the approved callout wording across all Prisma Next docs pages: invite users to try the cutting-edge next major version in Early Access and share feedback, and point anyone who wants the current GA release to Prisma 7. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: redefine Early Access on the ORM and Console lifecycle pages Early Access now means: ready to try out, cutting edge, and evolving with user feedback, with an API surface that won't change drastically. Removes the "prepared for significant breaking changes" framing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: soften Preview production language to match new Early Access meaning Keeps the Early Access -> Preview -> GA ladder monotonic: Preview is now described as close to stable, validate in staging, rather than "not recommended in production." Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: default /docs to Prisma Next and add callout title spacing - Redirect bare /docs to /docs/next so the docs land on Prisma Next by default. Keep the Prisma 7 (Latest) getting-started reachable at /docs/getting-started: repoint the getting-started version switcher's Latest target and the Getting Started tab there (bare "/" now redirects), and update the callouts' Prisma 7 links to /getting-started. - Add spacing under the callout title so the heading no longer sits flush against the body (applies to all callouts via CalloutTitle). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: fold Prisma Next into the getting-started sidebar Incorporate Ty's feedback on the Prisma Next getting-started docs: - Remove the auto-redirect from bare /docs to /docs/next; the docs now land on Introduction to Prisma. - Remove the "Docs version" dropdown on getting-started pages. Prisma Next lives inline in the getting-started sidebar as its own sections instead of a separate rooted version. The ORM version dropdown is unchanged. - Restructure the getting-started sidebar into: Getting Started, Get started with Prisma Next, Prisma Next (Quickstart + Add to Existing Project), Prisma ORM, and Prisma Postgres. - Add a Prisma Next entry to the Prisma Postgres > Quickstart dropdown; the page moves to /prisma-postgres/quickstart/prisma-next with a redirect from the old path. - Add a non-forceful Prisma Next callout on Introduction to Prisma. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: sharpen Prisma Next copy, add docs-writer skill + redirect tracking Goal 1: make Prisma Next more discoverable to readers and agents. Update the Prisma Next copy across the docs to the assertive standard line: "Prisma Next is the next major version of Prisma ORM, available now in Early Access. We strongly recommend trying it out before it becomes generally available..." Replaces the softer "we'd love for you to try it" callouts and the fluffy "Curious what's next?" intro note. Goal 2: move the prisma-docs-voice (docs writer) skill into the repo at .claude/skills/prisma-docs-voice and extend it for Prisma Next. The new references/prisma-next.md makes the Prisma Next repo the source of truth (fact-check every behavioral claim against packages/, examples/, docs/, and the installed agent skills before writing), follows the Prisma Next user-docs spec for information architecture, calls out deltas from Prisma 7, and refuses to guess when behavior is unclear. Goal 3: track redirects. references/redirects-tracking.md documents the URL migration model (Prisma Next ORM docs authored at /docs/orm/next, promoted to /docs/orm at GA, with Prisma 7 pinned to /docs/orm/v7) and the tracking-file format. apps/docs/prisma-next-redirects.md is the concrete decision log, seeded with this PR's moves. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Nurul Sundarani <sundarani@prisma.io> Co-authored-by: Ankur Datta <64993082+ankur-arch@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
No description provided.