Update image reference in management API guide

[petradonka]

Summary by CodeRabbit

• Documentation
  • Updated the Management API guide with a new cover image.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

Dangerous URL check

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

[coderabbitai]

Walkthrough

The Management API guide's header image reference is updated from a connection pooling image to a dedicated management API cover image, with a trailing newline formatting adjustment applied.

Changes

Cohort / File(s)	Summary
Documentation Header Update content/800-guides/330-management-api-basic.mdx	Image path changed from /img/guides/neon-connection-pooling.png to /img/guides/prisma-management-api-cover.png; trailing newline normalized

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file with straightforward image path replacement and formatting adjustment
• No logic changes or complex interdependencies

Possibly related PRs

• refactor: chore make management API docs more visible #7059: Modifies the same Management API guide file, updating internal link references alongside this PR's image path change.

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 and concisely describes the main change: updating an image reference in the management API documentation guide.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent 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 8526167 and 15c9a68.

📒 Files selected for processing (1)

• content/800-guides/330-management-api-basic.mdx (2 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:

• content/800-guides/330-management-api-basic.mdx

⏰ 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 (2)

content/800-guides/330-management-api-basic.mdx (2)

200-200: Trailing newline formatting is a solid addition.

The addition of a trailing newline aligns with POSIX standards and most repository linting best practices. This small hygiene fix is a nice touch.

---

6-6: Verified: new image asset exists and old image reference is properly managed.

Verification confirms the image swap is correct. The new asset (/img/guides/prisma-management-api-cover.png) exists and is in place. The old image (/img/guides/neon-connection-pooling.png) remains on filesystem, which is appropriate since it's actively referenced in another guide (310-neon-accelerate.mdx). The PR correctly replaces just this file's cover image without disturbing other parts of the docs. No issues here.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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]

original	preview
content/800-guides/330-management-api-basic.mdx	content/800-guides/330-management-api-basic.mdx

[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	2223
✅ Successful	2197
⏳ Timeouts	0
🔀 Redirected	2
👻 Excluded	23
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	1

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	15c9a68
Status:	✅  Deploy successful!
Preview URL:	https://1875581f.docs-51g.pages.dev
Branch Preview URL:	https://petradonka-patch-2.docs-51g.pages.dev

View logs