fix: get started page next button issue

[ankur-arch]

Summary by CodeRabbit

• Documentation
  • Enhanced navigation flow and pagination structure in getting started guides to improve content discoverability and user experience.

[coderabbitai]

Walkthrough

This PR adds pagination metadata fields to two MDX documentation files within the Getting Started section. A pagination_label field is added to the Quickstart page, and a pagination_next field is added to the Getting Started index page to establish navigation linkage between them.

Changes

Cohort / File(s)	Change Summary
Pagination Metadata Configuration content/100-getting-started/index.mdx, content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx	Added frontmatter fields: pagination_next (index) and pagination_label (quickstart page) to configure page navigation sequencing within the documentation structure.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify that the pagination_next reference path (getting-started/prisma-orm/quickstart/prisma-postgres) correctly points to the intended Quickstart page
• Confirm the pagination_label: 'Quickstart' value aligns with the intended navigation display text
• Ensure these frontmatter fields follow the established conventions and structure used elsewhere in the documentation

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 fix: updating pagination/navigation fields to resolve the 'next button' issue on the getting started page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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.

---

_{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	2235
✅ Successful	2205
⏳ Timeouts	0
🔀 Redirected	5
👻 Excluded	23
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	1

Errors per input

Errors in 200-orm/200-prisma-client/600-observability-and-logging/240-metrics.mdx

• [404] https://github.com/prisma/prisma/releases/tag/7.0.0 | Error (cached)

[cloudflare-workers-and-pages]

Deploying docs with    Cloudflare Pages

Latest commit:	0a614df
Status:	✅  Deploy successful!
Preview URL:	https://126147de.docs-51g.pages.dev
Branch Preview URL:	https://ankur-getting-started-patch.docs-51g.pages.dev

View logs

[coderabbitai]

Actionable comments posted: 1

📜 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 9212a24 and 0a614df.

📒 Files selected for processing (2)

• content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx (1 hunks)
• content/100-getting-started/index.mdx (1 hunks)

🧰 Additional context used

🧠 Learnings (4)

📚 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/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
• content/100-getting-started/index.mdx

📚 Learning: 2025-10-08T16:22:57.129Z

Learnt from: aidankmcalister
Repo: prisma/docs PR: 7165
File: content/800-guides/550-test-guide.mdx:50-66
Timestamp: 2025-10-08T16:22:57.129Z
Learning: In `.mdx` files, do NOT flag or suggest changes for the following code quality issues even if they represent poor practices: React anti-patterns (using var instead of useState, direct DOM manipulation), missing keys in .map() iterations, non-serializable props in getServerSideProps, unused variables, missing error handling, SQL injection vulnerabilities (unless actively showing how to fix them), insecure cookie settings, missing TypeScript types, PrismaClient instantiation patterns, or any other code quality, security, or performance issues. Documentation code snippets are copied from source code and often intentionally show "before" examples or common mistakes.

Applied to files:

• content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
• content/100-getting-started/index.mdx

📚 Learning: 2025-10-14T11:41:08.844Z

Learnt from: carlagn
Repo: prisma/docs PR: 7183
File: content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx:561-567
Timestamp: 2025-10-14T11:41:08.844Z
Learning: Ignore the file `content/200-orm/800-more/600-help-and-troubleshooting/050-dataguide/050-database-glossary.mdx` in future reviews as per user request. Issues in this file were addressed in PR #7185.

Applied to files:

• content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx

📚 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: Only flag code snippets for (1) exposed secrets with real-looking values that should be placeholders (e.g., API keys, database passwords, AWS credentials), or (2) blatant syntax errors like missing parentheses, brackets, braces, or mismatched delimiters. Do not flag code quality issues, anti-patterns, security vulnerabilities, missing error handling, unused variables, or any other bad practices, as documentation intentionally shows problematic code.

Applied to files:

• content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.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 (1)

content/100-getting-started/index.mdx (1)

8-8: The pagination path is correct—it follows the documented pattern across your entire codebase.

The verification confirms what your review comment suspected: numeric prefixes are indeed stripped during URL generation. I've checked multiple pagination_next entries throughout the documentation:

• content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx → getting-started/prisma-orm/quickstart/prisma-postgres ✓
• content/200-orm/800-more/300-upgrade-guides/... → orm/more/upgrade-guides/... ✓
• And several others—all follow the same pattern

The target file exists, your frontmatter is properly formatted, and the path aligns with how your documentation platform resolves these references throughout the codebase. Nothing needs to change here.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify that pagination_label is a recognized frontmatter field.

Line 4 adds pagination_label: 'Quickstart' to establish the navigation label for this page, complementing the pagination_next reference from the index page. The label is concise and appropriate. Ensure this field is recognized by your documentation platform's pagination/navigation system.

Include the pagination_label field in the verification script above by looking for how it's used elsewhere:

---

🏁 Script executed:

#!/bin/bash
# Description: Check pagination_label usage patterns

# Find all uses of pagination_label in the docs
rg -n 'pagination_label' content/ --type mdx

Length of output: 27

---

🏁 Script executed:

#!/bin/bash
# Description: Find pagination_label usage and related pagination fields

# Search for pagination_label without type specification
echo "=== Searching for pagination_label ==="
rg -n 'pagination_label' content/

# Search for pagination_ prefix to understand the pattern
echo -e "\n=== Searching for other pagination_ fields ==="
rg -n 'pagination_' content/ | head -20

# Look for pagination_next to understand the bidirectional reference
echo -e "\n=== Searching for pagination_next ==="
rg -n 'pagination_next' content/

Length of output: 3081

---

🏁 Script executed:

#!/bin/bash
# Description: Verify if pagination_label is a supported field

# Look for docusaurus configuration
echo "=== Looking for Docusaurus config files ==="
find content/ -name "docusaurus.config.*" -o -name "sidebar*" -o -name ".docusaurus*" 2>/dev/null | head -10

# Look for any documentation about frontmatter or pagination
echo -e "\n=== Searching for pagination documentation in files ==="
rg -n 'pagination_label|frontmatter|supported.*field' content/ --type-not json | head -15

# Check root directory for config
echo -e "\n=== Checking repository root for config files ==="
ls -la | grep -E 'docusaurus|config|\.doc'

# Look for any TypeScript/JS config in root
echo -e "\n=== Looking for docusaurus config at root ==="
find . -maxdepth 2 -name "docusaurus.config.js" -o -name "docusaurus.config.ts" 2>/dev/null

Length of output: 4429

---

---

🏁 Script executed:

#!/bin/bash
# Description: Understand how pagination system works (pagination_next context)

# Search for any custom pagination handling or plugins
echo "=== Looking for custom pagination implementation ==="
rg -n 'pagination' . --type ts --type js -g '!node_modules' --type-not mdx | head -20

# Check if there's a client plugin or theme customization for pagination
echo -e "\n=== Checking client-plugins directory ==="
find . -path ./node_modules -prune -o -type f -name "*pagination*" -print

# Look at a file that uses pagination_next to understand context
echo -e "\n=== Context around pagination_next usage ==="
rg -B 5 -A 5 'pagination_next' content/100-getting-started/index.mdx | head -20

# Check if pagination_label appears in any theme or plugin files
echo -e "\n=== Searching entire repo for pagination_label (not just content/) ==="
rg -n 'pagination_label' . -g '!node_modules' 2>/dev/null || echo "Only in target file"

Length of output: 779

---

Remove the unsupported pagination_label field—it's not recognized by the documentation platform.

The codebase uses pagination_next (defined in the index file) to establish pagination flow, but pagination_label is a new, undocumented field with no implementation. The official frontmatter specification (documented in content/800-guides/999-making-guides.mdx) lists only: title, metaTitle, description, sidebar_label, image, and community_section. Your docusaurus configuration contains no plugin or configuration to process custom pagination labels. This field will be silently ignored.

The existing pagination_next: getting-started/prisma-orm/quickstart/prisma-postgres in the index file already establishes the forward pagination link. Remove line 4 entirely.

🤖 Prompt for AI Agents

In
content/100-getting-started/02-prisma-orm/100-quickstart/100-prisma-postgres.mdx
around line 4, remove the unsupported frontmatter field "pagination_label:
'Quickstart'" entirely; ensure the surrounding frontmatter remains valid YAML
(no stray commas or broken separators) and rely on the existing pagination_next
in the index file for navigation.