Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
WalkthroughThis PR updates SEO and Open Graph metadata (titles and descriptions) across 15 page routes in the Prisma site application. All changes are isolated to exported metadata declarations with no modifications to page logic or component behavior. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (2)
apps/site/src/app/oss-friends/page.tsx (1)
4-6: Title format differs from other pages.This uses
"Prisma | Our OSS Friends"(brand prefix) while other pages in this PR use a brand suffix pattern like"Page Name | Prisma". If intentional, that's fine—just flagging for awareness in case you want consistent SEO patterns across the site.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/site/src/app/oss-friends/page.tsx` around lines 4 - 6, The page metadata title in the export const metadata created via createPageMetadata currently uses a brand-prefix pattern ("Prisma | Our OSS Friends"); update it to match the project's consistent brand-suffix pattern by switching the title to "Our OSS Friends | Prisma" in the createPageMetadata call (or explicitly confirm in PR comment if the prefix pattern is intentional and should differ).apps/site/src/app/studio/page.tsx (1)
90-118: Consider shortening the title for better search result display.The updated metadata is correctly structured and consistently applied across all fields (main, OpenGraph, Twitter). However, the new title at ~68 characters exceeds the typical 50-60 character limit that search engines display in results. This means users will see a truncated version like:
"Prisma Studio | Next-generation ORM for Node.js and Type..."While the current title is excellent for keyword coverage, you might achieve better click-through rates with a more concise version that displays fully in search results, such as:
"Prisma Studio | Next-gen ORM for Node.js & TypeScript"(~56 chars)"Prisma Studio | Modern ORM for Node.js and TypeScript"(~58 chars)That said, longer titles still contribute to SEO rankings even when truncated, so this is more of an optimization than a fix.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@apps/site/src/app/studio/page.tsx` around lines 90 - 118, Shorten the metadata.title (and the same title in openGraph.title and twitter.title) to a more concise string under ~60 characters to avoid truncation in search results; update the exported constant metadata's title property (and mirror values in openGraph.title and twitter.title) to a shorter option like "Prisma Studio | Next‑gen ORM for Node.js & TypeScript" or similar while keeping descriptions and image fields unchanged.
🤖 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/site/src/app/event-code-of-conduct/page.tsx`:
- Around line 10-12: Update the metadata in page.tsx: change the description
string to include the missing verb (e.g., "Read our Event Code of Conduct and
see how it relates to you.") and rename the title from "Prisma - Event Code of
Conduct" to use the consistent suffix format "Event Code of Conduct | Prisma" so
it matches other pages; modify the exported title and description values
accordingly.
In `@apps/site/src/app/events/page.tsx`:
- Around line 17-18: The page description string (the description field in
apps/site/src/app/events/page.tsx) contains a duplicated "and" and awkward
phrasing; update the description value to remove the duplicate and improve flow
to match the hero copy tone (see the hero/heading text used later in the same
file) — rewrite the description to something like "Upcoming events, meetups, and
conferences, and explore content from previous events" or a concise variant that
mirrors the hero copy style so it reads smoothly and consistently.
In `@apps/site/src/app/showcase/page.tsx`:
- Line 15: The SHOWCASE_TITLE constant currently contains inconsistent
capitalization ("Customer Success stories"); update the string value of
SHOWCASE_TITLE to use title case for "Stories" (e.g., "Prisma Showcase |
Customer Success Stories") so the site title is consistently capitalized.
In `@apps/site/src/app/stack/page.tsx`:
- Around line 14-15: The string constant description includes an unnecessary
comma before "and frameworks"; update the value of description (the constant
named description in page.tsx) to remove the extra comma so the sentence reads:
"Prisma is a Node.js and TypeScript ORM that integrates easily with popular
databases and frameworks."
In `@apps/site/src/app/terms/page.tsx`:
- Around line 6-8: Update the page metadata in page.tsx: change the description
string from "Read our terms of services and see how they relate to you." to
"Read our terms of service and see how they relate to you." and append the brand
suffix to the title value so title becomes "Terms of Service | Prisma" (or the
project's standard suffix); modify the exported title and description values in
this file (the title and description metadata) accordingly to match other pages.
In `@apps/site/src/app/typedsql/page.tsx`:
- Around line 102-108: Update the metadata object created by createPageMetadata
(exported as metadata) to fix text issues: remove the trailing space at the end
of the title string, change "fully type-safety" to "full type-safety", and
capitalize "SQL" wherever "sql" appears (e.g., in the title and description).
Ensure these edits are applied to the title and description fields inside the
metadata object.
---
Nitpick comments:
In `@apps/site/src/app/oss-friends/page.tsx`:
- Around line 4-6: The page metadata title in the export const metadata created
via createPageMetadata currently uses a brand-prefix pattern ("Prisma | Our OSS
Friends"); update it to match the project's consistent brand-suffix pattern by
switching the title to "Our OSS Friends | Prisma" in the createPageMetadata call
(or explicitly confirm in PR comment if the prefix pattern is intentional and
should differ).
In `@apps/site/src/app/studio/page.tsx`:
- Around line 90-118: Shorten the metadata.title (and the same title in
openGraph.title and twitter.title) to a more concise string under ~60 characters
to avoid truncation in search results; update the exported constant metadata's
title property (and mirror values in openGraph.title and twitter.title) to a
shorter option like "Prisma Studio | Next‑gen ORM for Node.js & TypeScript" or
similar while keeping descriptions and image fields unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 5e380d7f-0965-47a0-afb7-966d79d4d602
📒 Files selected for processing (17)
apps/site/src/app/about/page.tsxapps/site/src/app/client/page.tsxapps/site/src/app/ecosystem/page.tsxapps/site/src/app/event-code-of-conduct/page.tsxapps/site/src/app/events/page.tsxapps/site/src/app/migrate/page.tsxapps/site/src/app/newsletter/page.tsxapps/site/src/app/oss-friends/page.tsxapps/site/src/app/partners/page.tsxapps/site/src/app/pricing/page.tsxapps/site/src/app/showcase/page.tsxapps/site/src/app/sla/page.tsxapps/site/src/app/stack/page.tsxapps/site/src/app/studio/page.tsxapps/site/src/app/support-policy/page.tsxapps/site/src/app/terms/page.tsxapps/site/src/app/typedsql/page.tsx
Comment on lines
+10
to
+12
| title: "Prisma - Event Code of Conduct", | ||
| description: | ||
| "All attendees, speakers, sponsors, and volunteers at Prisma events are required to agree to this code of conduct.", | ||
| "Read our Event Code of Conduct and how it relates to you.", |
Contributor
There was a problem hiding this comment.
Grammar issue and title format inconsistency.
Two observations:
- The description is missing a verb: "and how it relates" should be "and see how it relates" (matching the support-policy page pattern).
- This page uses
"Prisma - ..."prefix while most other pages in this PR use"... | Prisma"suffix. Consider aligning for consistency.
✏️ Suggested fix
export const metadata = createPageMetadata({
- title: "Prisma - Event Code of Conduct",
+ title: "Event Code of Conduct | Prisma",
description:
- "Read our Event Code of Conduct and how it relates to you.",
+ "Read our Event Code of Conduct and see how it relates to you.",
path: "/event-code-of-conduct",📝 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.
Suggested change
| title: "Prisma - Event Code of Conduct", | |
| description: | |
| "All attendees, speakers, sponsors, and volunteers at Prisma events are required to agree to this code of conduct.", | |
| "Read our Event Code of Conduct and how it relates to you.", | |
| title: "Event Code of Conduct | Prisma", | |
| description: | |
| "Read our Event Code of Conduct and see how it relates to you.", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/event-code-of-conduct/page.tsx` around lines 10 - 12,
Update the metadata in page.tsx: change the description string to include the
missing verb (e.g., "Read our Event Code of Conduct and see how it relates to
you.") and rename the title from "Prisma - Event Code of Conduct" to use the
consistent suffix format "Event Code of Conduct | Prisma" so it matches other
pages; modify the exported title and description values accordingly.
Comment on lines
17
to
+18
| description: | ||
| "Find upcoming Prisma events and Meetups, see where the team will be speaking, and explore recordings and resources from past events.", | ||
| "Upcoming events or meetups, conferences and and explore the content from previous events.", |
Contributor
There was a problem hiding this comment.
Fix duplicate "and" and improve sentence structure.
The description contains "and and" (duplicate word) and reads awkwardly. Consider something closer to the page's hero copy on line 62-65 for consistency.
✏️ Suggested fix
description:
- "Upcoming events or meetups, conferences and and explore the content from previous events.",
+ "Find upcoming Prisma events and meetups, see where we'll be speaking, and explore content from previous events.",📝 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.
Suggested change
| description: | |
| "Find upcoming Prisma events and Meetups, see where the team will be speaking, and explore recordings and resources from past events.", | |
| "Upcoming events or meetups, conferences and and explore the content from previous events.", | |
| description: | |
| "Find upcoming Prisma events and meetups, see where we'll be speaking, and explore content from previous events.", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/events/page.tsx` around lines 17 - 18, The page description
string (the description field in apps/site/src/app/events/page.tsx) contains a
duplicated "and" and awkward phrasing; update the description value to remove
the duplicate and improve flow to match the hero copy tone (see the hero/heading
text used later in the same file) — rewrite the description to something like
"Upcoming events, meetups, and conferences, and explore content from previous
events" or a concise variant that mirrors the hero copy style so it reads
smoothly and consistently.
|
|
||
| const SHOWCASE_TITLE = "Made with Prisma"; | ||
| const SHOWCASE_DESCRIPTION = "Learn how companies use Prisma in production"; | ||
| const SHOWCASE_TITLE = "Prisma Showcase | Customer Success stories"; |
Contributor
There was a problem hiding this comment.
Inconsistent capitalization in title.
"Customer Success stories" mixes title case with lowercase. For consistency, capitalize "Stories" as well.
✏️ Suggested fix
-const SHOWCASE_TITLE = "Prisma Showcase | Customer Success stories";
+const SHOWCASE_TITLE = "Prisma Showcase | Customer Success Stories";📝 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.
Suggested change
| const SHOWCASE_TITLE = "Prisma Showcase | Customer Success stories"; | |
| const SHOWCASE_TITLE = "Prisma Showcase | Customer Success Stories"; |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/showcase/page.tsx` at line 15, The SHOWCASE_TITLE constant
currently contains inconsistent capitalization ("Customer Success stories");
update the string value of SHOWCASE_TITLE to use title case for "Stories" (e.g.,
"Prisma Showcase | Customer Success Stories") so the site title is consistently
capitalized.
Comment on lines
14
to
+15
| const description = | ||
| "Prisma works with every major TypeScript stack. Explore how Prisma fits Next.js, NestJS, GraphQL, your database, and more."; | ||
| "Prisma is a Node.js and TypeScript ORM that integrates easily with popular databases, and frameworks."; |
Contributor
There was a problem hiding this comment.
Remove the unnecessary comma before "and frameworks".
There's a spurious comma separating "databases" from "and frameworks" that disrupts the sentence flow.
✏️ Suggested fix
const description =
- "Prisma is a Node.js and TypeScript ORM that integrates easily with popular databases, and frameworks.";
+ "Prisma is a Node.js and TypeScript ORM that integrates easily with popular databases and frameworks.";🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/stack/page.tsx` around lines 14 - 15, The string constant
description includes an unnecessary comma before "and frameworks"; update the
value of description (the constant named description in page.tsx) to remove the
extra comma so the sentence reads: "Prisma is a Node.js and TypeScript ORM that
integrates easily with popular databases and frameworks."
Comment on lines
+6
to
+8
| title: "Terms of Service", | ||
| description: | ||
| "Read the Prisma Terms of Service governing your use of Prisma products and services.", | ||
| "Read our terms of services and see how they relate to you.", |
Contributor
There was a problem hiding this comment.
Grammatical error: "terms of services" should be "terms of service".
The phrase "terms of service" is a fixed expression and should remain singular. Additionally, the title lacks the brand suffix (e.g., | Prisma) that other pages use for consistent branding.
✏️ Suggested fix
export const metadata = createPageMetadata({
- title: "Terms of Service",
+ title: "Terms of Service | Prisma",
description:
- "Read our terms of services and see how they relate to you.",
+ "Read our terms of service and see how they relate to you.",
path: "/terms",📝 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.
Suggested change
| title: "Terms of Service", | |
| description: | |
| "Read the Prisma Terms of Service governing your use of Prisma products and services.", | |
| "Read our terms of services and see how they relate to you.", | |
| title: "Terms of Service | Prisma", | |
| description: | |
| "Read our terms of service and see how they relate to you.", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/terms/page.tsx` around lines 6 - 8, Update the page
metadata in page.tsx: change the description string from "Read our terms of
services and see how they relate to you." to "Read our terms of service and see
how they relate to you." and append the brand suffix to the title value so title
becomes "Terms of Service | Prisma" (or the project's standard suffix); modify
the exported title and description values in this file (the title and
description metadata) accordingly to match other pages.
Comment on lines
102
to
108
| export const metadata = createPageMetadata({ | ||
| title: "TypedSQL | Fully type-safe raw SQL for Prisma ORM", | ||
| title: "TypedSQL: Fully type-safe raw SQL in Prisma ORM ", | ||
| description: | ||
| "Use TypedSQL with Prisma ORM for fully type-safe raw SQL queries with autocomplete, better ergonomics, and the full power of SQL.", | ||
| "Write raw sql queries with fully type-safety and auto-completion in Prisma ORM. Get type-safe database queries without sacrificing the power and flexibility of raw SQL.", | ||
| path: "/typedsql", | ||
| ogImage: "/og/og-typedsql.png", | ||
| }); |
Contributor
There was a problem hiding this comment.
Multiple text issues in the metadata.
A few things to clean up here:
- Trailing space in the title (Line 103)
- Grammar: "fully type-safety" should be "full type-safety" (adjective, not adverb before a noun)
- Capitalization: "raw sql" should be "raw SQL" (SQL is an acronym)
✏️ Suggested fix
export const metadata = createPageMetadata({
- title: "TypedSQL: Fully type-safe raw SQL in Prisma ORM ",
+ title: "TypedSQL: Fully type-safe raw SQL in Prisma ORM",
description:
- "Write raw sql queries with fully type-safety and auto-completion in Prisma ORM. Get type-safe database queries without sacrificing the power and flexibility of raw SQL.",
+ "Write raw SQL queries with full type-safety and auto-completion in Prisma ORM. Get type-safe database queries without sacrificing the power and flexibility of raw SQL.",
path: "/typedsql",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/src/app/typedsql/page.tsx` around lines 102 - 108, Update the
metadata object created by createPageMetadata (exported as metadata) to fix text
issues: remove the trailing space at the end of the title string, change "fully
type-safety" to "full type-safety", and capitalize "SQL" wherever "sql" appears
(e.g., in the title and description). Ensure these edits are applied to the
title and description fields inside the metadata object.
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.
Summary by CodeRabbit