Rebrand Prisma Next to Prisma 8 across docs, blog, and site - #8117
Open
nurul3101 wants to merge 2 commits into
Open
Rebrand Prisma Next to Prisma 8 across docs, blog, and site#8117nurul3101 wants to merge 2 commits into
nurul3101 wants to merge 2 commits into
Conversation
Contributor
|
Important Review skippedToo many files! This PR contains 187 files, which is 37 over the limit of 150. To get a review, narrow the scope: Upgrade to Pro+ to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (33)
📒 Files selected for processing (187)
You can disable this status message by setting the Comment |
Contributor
🍈 Lychee Link Check Report805 links: ✅ All links are working!Full Statistics Table
|
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
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.
nurul3101
force-pushed
the
prisma-8-rebrand
branch
from
July 30, 2026 10:49
1eac8ea to
b5ec2ad
Compare
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.
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
1 participant
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.
Prisma Next is now named Prisma 8, and its stage is framed as a Release Candidate rather than Early Access. This PR replaces the working name everywhere users read it (docs, blog, marketing site, and the images that carried the old wordmark) and updates the status framing in a second commit.
Commit 1: the rename
Content and labels
apps/docs,apps/blog, andapps/site(146 MDX files).llms.txttopic titles. Sidebar version matchers accept the new labels and keep their URL fallbacks.content-write-bloganddocs-writerskill conventions, hero-image skill logo lockups renamed toprisma-8-*with tokens/README updates, CONTRIBUTING.md.Images (14 replaced)
meta.pngwas re-rendered from its hero.prisma-8.png, old file removed).Commit 2: Early Access becomes Release Candidate
Everywhere the site describes Prisma 8's current stage now says the Release Candidate is available:
llms.txttopics, the standard status callout on nine pages, and status prose across the next tree.release-candidatebadge type (badge-types.tsdrives the zod enum, label, and color maps); the 41 Prisma 8 pages switched to it. The Postgres serverless driver keeps itsearly-accessbadge and the generic feature-maturity docs are untouched.pris.ly/pn-ealink text; site stack page descriptions.Kept as historical artifacts (they describe the June Early Access launch as an event): 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 (Prisma Postgres EA, Optimize EA, legal terms, maturity-tier docs).
Deliberately unchanged
Product-owned identifiers and live URLs keep the working name until their owners change them:
npm create prisma@next/prisma@nextdist-tags, theprisma-nextCLI binary,prisma-next.config.ts, the@prisma-next/*npm scope, scaffolded skill names (prisma-next-queries, ...), and theprisma/prisma-nextGitHub repo./docs/orm/next/,/docs/cli/next/,/docs/guides/next/URL segments: the commented GA cutover plan inapps/docs/next.config.mjsalready covers their future move./blog/prisma-next-*),pris.ly/pn-*short links, Discord#prisma-nextchannel names, UTM campaign tags.prisma-next-banner*): PostHog CTA click actions target these selectors.Verification
types:checkgreen for docs and blog (site andpackages/eclipsehave pre-existing failures unrelated to this PR, reproduced on a clean tree).lint:links,lint:agent-ready,test:llm-markdown,lint:spellcheck(778 files, 0 issues), andpnpm checkall pass after both commits.Possible follow-ups (not in this PR)
prisma-next-*blog slugs with 301s (kept for SEO/link continuity).pris.ly/p8-*aliases; product-side renames (CLI, npm scope, Discord) when the ORM repo rebrands.feat/prisma-next-referencebranch will need the same rename and framing when it lands.