blog: add product callouts to two ORM posts#7983
Conversation
Add coherent in-context callouts and CTAs to two ranking ORM blog posts, pointing readers to Prisma Next, the individual posts/series, and our commercial products (Prisma Postgres + Prisma Compute). - backend-prisma-typescript-orm-with-postgresql-data-modeling: series navigation, a Prisma Postgres alternative to local Docker at the DB setup step, and a closing note on Prisma Next + Postgres/Compute. - why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-change: tie the node_modules change to Prisma Next, and a new-project callout for Prisma Postgres + Compute. Callouts use the repo's ::: directive syntax; Compute is marked public beta throughout. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
WalkthroughTwo blog posts were updated with new and rewritten MDX callouts. One adds series navigation, a Docker alternative, and version guidance. The other revises Prisma Client generation explanations and adds Prisma Next and Prisma Postgres references. ChangesBlog content updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
| - Compliance with the assumption that `node_modules` can only be modified by package managers. | ||
|
|
||
| :::note[Part of a bigger change] | ||
| Getting the generated client out of `node_modules` is one piece of a bigger change. [Prisma Next](https://www.prisma.io/blog/the-next-evolution-of-prisma-orm) takes the idea all the way: you keep a single data contract, and the generated client lands in your source tree as normal code. You can read it, commit it, and bundle it like anything else, never hidden in `node_modules`. |
There was a problem hiding this comment.
I'm not sure how this connects.
There was a problem hiding this comment.
Reworked this callout — it no longer jumps to "data contract" (off-topic for this article). It now bridges directly from the v7 output-path change to Prisma Next: the same principle (treat the generated client as ordinary source code in your project, not something hidden in node_modules), carried forward into the next major version.
| As always, [reach out to us on X](https://pris.ly/x) or [join our Discord](https://pris.ly/discord) if you have any feedback or questions! | ||
|
|
||
| :::ppg[Starting a new project?] | ||
| If you're setting an `output` path on a new project as suggested above, the database and hosting can come from the same place. [Prisma Postgres](https://www.prisma.io/postgres) gives you a managed Postgres database, and [Prisma Compute](https://www.prisma.io/compute) (public beta) runs your TypeScript app next to it. The ORM itself is heading toward [Prisma Next](https://www.prisma.io/blog/the-next-evolution-of-prisma-orm). |
There was a problem hiding this comment.
not sure how this connects.
There was a problem hiding this comment.
Reconnected to the article's own "starting a new project today" advice. If you're setting an output path on a fresh project, you still need a database for DATABASE_URL to point at — so the callout now leads with npx create-db (Prisma Postgres), then Prisma Compute for hosting, then Prisma Next for where the ORM goes after v7.
| > **Note**: If you don't want to use Docker, you can set up a [local PostgreSQL database](https://www.prisma.io/dataguide/postgresql/setting-up-a-local-postgresql-database) or a [hosted PostgreSQL database on Heroku](https://dev.to/prisma/how-to-setup-a-free-postgresql-database-on-heroku-1dc1). | ||
|
|
||
| :::ppg[Don't want to run Docker?] | ||
| The tutorial runs Postgres in a local container, which still works. If you'd rather skip that, create a [Prisma Postgres](https://www.prisma.io/postgres) database and use its connection string as your `DATABASE_URL`. Every schema, migration, and query step below is the same either way. |
There was a problem hiding this comment.
You can use local prisma postgres or npx create-db, provide back links to our docs.
There was a problem hiding this comment.
Done. The callout now points to npx create-db (https://www.prisma.io/docs/postgres/introduction/npx-create-db) and local Prisma Postgres (https://www.prisma.io/docs/postgres/database/local-development), both linked to docs, with the connection string going straight into DATABASE_URL.
Address review comments and improve the article writing: - node_modules post: reconnect both callouts to the article's actual thread (generated-code location, not a "data contract"). The mid callout now bridges from the v7 output-path change to Prisma Next; the closing callout ties to the post's own "new project" advice via DATABASE_URL + npx create-db, then Prisma Compute and Prisma Next. - node_modules post: copy-edit pass preserving author voice. Fix the "develoeprs" typo and the broken "aware of their structure" antecedent, remove the em dash (house style), and tighten several long sentences. - data-modeling post: the Docker-alternative callout now points to `npx create-db` and local Prisma Postgres, each linked to its docs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Give Prisma Compute a clear, contextual mention rather than a buried list item: serverless TypeScript hosting (public beta) that runs the app on the same infrastructure as the Prisma Postgres database. In the data-modeling series this ties to the deployment installment (part 4). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
What
Adds coherent, in-context callouts and CTAs to two ranking ORM blog posts, per the "Update & Optimize" SEO task. Each callout leads with something useful to the reader and ties to the surrounding content rather than reading like a launch email.
backend-prisma-typescript-orm-with-postgresql-data-modeling(series part 1)why-prisma-orm-generates-code-into-node-modules-and-why-it-ll-changenode_moduleschange to Prisma Next.outputpath.Notes
:::directive syntax (ppg/note/tip), all balanced.🤖 Generated with Claude Code
Summary by CodeRabbit