Conversation
WalkthroughA new MDX blog post was added documenting the Prisma Docs rebuild: metadata-rich front matter and full article content covering the Fumadocs migration, search and AI chat updates, versioned docs, launch strategy, user/contributor impact, and lessons learned. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx`:
- Line 28: Change the phrase "Like many open source projects" to hyphenate the
compound adjective: update the sentence in the document (the line containing
"Like many open source projects, our docs had grown fast.") so it reads "Like
many open-source projects, our docs had grown fast." ensuring "open-source" is
hyphenated wherever it directly modifies "projects."
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 3be9df3b-5826-4b15-9e5a-015039a14357
⛔ Files ignored due to path filters (5)
apps/blog/content/blog/rebuilding-the-prisma-docs/imgs/aichat.gifis excluded by!**/*.gifapps/blog/content/blog/rebuilding-the-prisma-docs/imgs/hero.pngis excluded by!**/*.pngapps/blog/content/blog/rebuilding-the-prisma-docs/imgs/homepage.pngis excluded by!**/*.pngapps/blog/content/blog/rebuilding-the-prisma-docs/imgs/meta.pngis excluded by!**/*.pngapps/blog/content/blog/rebuilding-the-prisma-docs/imgs/search.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx
|
|
||
| ## Why rebuild? | ||
|
|
||
| Like many open source projects, our docs had grown fast. When features shipped, docs followed quickly. That's mostly good, but over time the structure became harder to navigate and harder to trust — meaning outdated or duplicated content was easy to miss. |
There was a problem hiding this comment.
Hyphenate "open-source" when used as a compound adjective.
When "open source" modifies a noun directly (here, "projects"), it should be hyphenated as "open-source projects." This is a common grammatical convention for compound adjectives preceding nouns.
📝 Proposed fix
-Like many open source projects, our docs had grown fast.
+Like many open-source projects, our docs had grown fast.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Like many open source projects, our docs had grown fast. When features shipped, docs followed quickly. That's mostly good, but over time the structure became harder to navigate and harder to trust — meaning outdated or duplicated content was easy to miss. | |
| Like many open-source projects, our docs had grown fast. When features shipped, docs followed quickly. That's mostly good, but over time the structure became harder to navigate and harder to trust — meaning outdated or duplicated content was easy to miss. |
🧰 Tools
🪛 LanguageTool
[grammar] ~28-~28: Use a hyphen to join words.
Context: ...oyable. ## Why rebuild? Like many open source projects, our docs had grown fast...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx` at line 28,
Change the phrase "Like many open source projects" to hyphenate the compound
adjective: update the sentence in the document (the line containing "Like many
open source projects, our docs had grown fast.") so it reads "Like many
open-source projects, our docs had grown fast." ensuring "open-source" is
hyphenated wherever it directly modifies "projects."
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx (1)
27-27:⚠️ Potential issue | 🟡 MinorHyphenate “open-source” in this sentence.
When it directly modifies “projects,” this should read “open-source projects.”
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx` at line 27, Update the sentence containing the phrase "Like many open source projects" to hyphenate "open-source" so it reads "Like many open-source projects" — locate that exact sentence in the blog content (the line starting with "Like many open source projects, our docs had grown fast.") and apply the hyphenation change.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx`:
- Line 61: Update the sentence that currently mentions only "Cmd-K" and "Cmd-I"
to include Windows/Linux equivalents (e.g., "Cmd-K (Mac) / Ctrl-K
(Windows/Linux)" and "Cmd-I (Mac) / Ctrl-I (Windows/Linux)") or rephrase to note
these are Mac shortcuts and include Ctrl variants; locate the line containing
the literal "Cmd-K" and "Cmd-I" in the MDX content and change the wording to
present both platform variants or an explicit platform-specific note.
---
Duplicate comments:
In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx`:
- Line 27: Update the sentence containing the phrase "Like many open source
projects" to hyphenate "open-source" so it reads "Like many open-source
projects" — locate that exact sentence in the blog content (the line starting
with "Like many open source projects, our docs had grown fast.") and apply the
hyphenation change.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 6ddde4fc-3198-439f-8d50-2a5c02de2dbd
⛔ Files ignored due to path filters (5)
apps/blog/public/rebuilding-the-prisma-docs/imgs/aichat.gifis excluded by!**/*.gifapps/blog/public/rebuilding-the-prisma-docs/imgs/hero.pngis excluded by!**/*.pngapps/blog/public/rebuilding-the-prisma-docs/imgs/homepage.pngis excluded by!**/*.pngapps/blog/public/rebuilding-the-prisma-docs/imgs/meta.pngis excluded by!**/*.pngapps/blog/public/rebuilding-the-prisma-docs/imgs/search.pngis excluded by!**/*.png
📒 Files selected for processing (1)
apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx
|
|
||
| When we evaluated it as a team, our old docs immediately felt dated by comparison. So we went all in: not just a framework swap, but a full redesign of the UI, colors, and fonts. | ||
|
|
||
| We also surfaced Search and Chat with keyboard shortcuts, `Cmd-K` for search and `Cmd-I` for chat. |
There was a problem hiding this comment.
Include Windows/Linux shortcut equivalents.
Calling out only Cmd-K and Cmd-I reads as Mac-only. Add the Ctrl variants too, or phrase this as platform-specific shortcuts.
✏️ Suggested wording
-We also surfaced Search and Chat with keyboard shortcuts, `Cmd-K` for search and `Cmd-I` for chat.
+We also surfaced Search and Chat with keyboard shortcuts: `Cmd-K` / `Ctrl-K` for search and `Cmd-I` / `Ctrl-I` for chat.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| We also surfaced Search and Chat with keyboard shortcuts, `Cmd-K` for search and `Cmd-I` for chat. | |
| We also surfaced Search and Chat with keyboard shortcuts: `Cmd-K` / `Ctrl-K` for search and `Cmd-I` / `Ctrl-I` for chat. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/blog/content/blog/rebuilding-the-prisma-docs/index.mdx` at line 61,
Update the sentence that currently mentions only "Cmd-K" and "Cmd-I" to include
Windows/Linux equivalents (e.g., "Cmd-K (Mac) / Ctrl-K (Windows/Linux)" and
"Cmd-I (Mac) / Ctrl-I (Windows/Linux)") or rephrase to note these are Mac
shortcuts and include Ctrl variants; locate the line containing the literal
"Cmd-K" and "Cmd-I" in the MDX content and change the wording to present both
platform variants or an explicit platform-specific note.
Summary by CodeRabbit