Update label for Prisma Postgres tab

[petradonka]

Summary by CodeRabbit

• Documentation
  • Updated tab label to more accurately reflect Prisma's managed Postgres offering
  • Revised tab description to emphasize scaling capabilities, deeper integration with Prisma ORM and Studio, and free tier availability

[coderabbitai]

Walkthrough

Updated the first tab's label and description in the index data configuration. The label was changed to clarify Prisma's managed Postgres offering, and the description was revised to emphasize scaling to zero and deeper Prisma ORM integration while removing specific caching mentions.

Changes

Cohort / File(s)	Summary
Prisma Postgres tab updates src/data/indexData.ts	Updated first tab label from "Use Prisma Postgres" to "Use Prisma's managed Postgres"; revised description to emphasize scaling to zero and Prisma ORM/Studio integration, removing explicit built-in caching reference

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

• Changes are limited to copy and label updates with no logic modifications
• Single file affected with straightforward textual edits

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the label for the Prisma Postgres tab from 'Use Prisma Postgres' to 'Use Prisma's managed Postgres'.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Dangerous URL check

No absolute URLs to prisma.io/docs found.
No local URLs found.

[github-actions]

Redirect check

This PR probably requires the following redirects to be added to static/_redirects:

• This PR does not change any pages in a way that would require a redirect.

[github-actions]

🍈 Lychee Link Check Report

Note: Links are cached for 5 minutes. Failed links (timeouts, rate limits) are retried in a second run with longer timeout.

📊 Results Overview

Status	Count
🔍 Total	2413
✅ Successful	2386
⏳ Timeouts	0
🔀 Redirected	3
👻 Excluded	22
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	1

Errors per input

Errors in 200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx

• [ERROR] https://opentelemetry.io/docs/specs/otel/trace/tracestate-probability-sampling/ | Error (cached)

Redirects per input

Redirects in 800-guides/370-bun.mdx

• [429] https://pris.ly/bun-guide-example | Redirect: Followed 1 redirect resolving to the final status of: Too Many Requests. Redirects: https://pris.ly/bun-guide-example --> https://github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/bun-with-prisma-driver-adapters
• [429] https://pris.ly/bun_ppg_example | Redirect: Followed 1 redirect resolving to the final status of: Too Many Requests. Redirects: https://pris.ly/bun_ppg_example --> https://github.com/prisma/prisma-examples/tree/latest/generator-prisma-client/bun

Redirects in 800-guides/380-vercel-app-deployment.mdx

• [429] https://pris.ly/vercel_app_deployment_demo?utm_source=docs | Redirect: Followed 1 redirect resolving to the final status of: Too Many Requests. Redirects: https://pris.ly/vercel_app_deployment_demo?utm_source=docs --> https://github.com/prisma/vercel-deployment-claim-demo?utm_source=docs&utm_campaign=vercel_app_deployment
  Full Github Actions output

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/data/indexData.ts (1)

130-130: Consider reducing redundancy in the description.

The description mentions "Prisma Postgres" twice in quick succession, which feels a bit redundant. Consider consolidating to improve readability.

Example refactor:

     description:
-      "Get started with your favorite framework and Prisma Postgres. <b>With Prisma Postgres</b> you get an instant, fully hosted high-performance database that scales to zero and integrates deeply with Prisma ORM and Prisma Studio—all backed by a generous free tier.",
+      "Get started with your favorite framework and <b>Prisma Postgres</b>—an instant, fully hosted high-performance database that scales to zero and integrates deeply with Prisma ORM and Prisma Studio, all backed by a generous free tier.",

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 736f5af and bd366a8.

📒 Files selected for processing (1)

• src/data/indexData.ts (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-10-08T16:23:00.388Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:85-90
Timestamp: 2025-10-08T16:23:00.388Z
Learning: For .mdx files in the prisma/docs repository: All headings and titles should use sentence case (e.g., "Getting started with Prisma ORM", "Best practices for authentication"), not title case. Exception: Always preserve exact casing for product names including "Prisma Postgres", "Prisma", "Prisma ORM", and "Prisma Data Platform".

Applied to files:

• src/data/indexData.ts

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Check internal links
• GitHub Check: Cloudflare Pages

🔇 Additional comments (1)

src/data/indexData.ts (1)

128-128: Label clarification is helpful.

The updated label effectively clarifies that this is Prisma's managed database offering, making it easier for users to understand the distinction between the two tabs.

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	bd366a8
Status:	✅  Deploy successful!
Preview URL:	https://c7ba7c47.docs-51g.pages.dev
Branch Preview URL:	https://petradonka-patch-2.docs-51g.pages.dev

View logs