feat(blog): add Prisma Compute posts

[AmanVarshney01]

Summary

• add a create-prisma blog post covering Compute-ready scaffolding, Prisma Postgres, Prisma Skills add-ons, and redeploys
• add an inline VHS-rendered terminal image for the create-prisma flow, stored under apps/blog/public
• add a Prisma Compute TypeScript config blog post covering typed config, monorepos, agent skills, .prisma/local.json project resolution, and the migration path toward prisma.config.ts
• add compute as an allowed blog tag

Validation

• pnpm --filter blog types:check passes
• MIXEDBREAD_API_KEY=dummy pnpm --filter blog build passes
• pnpm --filter blog lint:links still reports pre-existing failures in older posts; the two new drafts are not in the failure list

Summary by CodeRabbit

• Documentation
  • Added guides for Prisma Compute deployments, including configuration setup and app scaffolding options.
  • Introduced new "compute" category tag for blog content organization.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jun 17, 2026 10:54am
docs	Ready	Preview, Comment	Jun 17, 2026 10:54am
eclipse	Ready	Preview, Comment	Jun 17, 2026 10:54am
site	Ready	Preview, Comment	Jun 17, 2026 10:54am

[coderabbitai]

Walkthrough

Two new MDX blog posts are added to the blog app: one announcing the Compute-ready scaffolding path in create-prisma, and one documenting the prisma.compute.ts typed config file and defineComputeConfig API. The blogPosts frontmatter tag schema in source.config.ts is extended to allow the "compute" tag value.

Changes

Prisma Compute Blog Content

Layer / File(s)

Summary

Blog tag schema extension and Compute blog posts apps/blog/source.config.ts, apps/blog/content/blog/create-prisma-deploy-prisma-compute/index.mdx, apps/blog/content/blog/prisma-compute-config-file/index.mdx

"compute" is added to the tags enum in the blogPosts frontmatter schema. Two new MDX posts are added: one covering the create-prisma Compute scaffolding path (generated files, optional add-ons, compute:deploy script, and defineComputeConfig example), and one documenting the typed prisma.compute.ts config file with single-app and monorepo defineComputeConfig examples, deploy selection behavior, agent-skill integration, and scope limits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• prisma/web#7942: Adds Prisma Compute-focused blog MDX content that the new "compute" frontmatter tag in this PR is directly designed to support.
• prisma/web#7950: Covers Prisma Compute configuration and deploy reference docs with framework listings that directly overlap with the prisma.compute.ts config post added here.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'feat(blog): add Prisma Compute posts' directly and accurately summarizes the main change—adding two new blog posts about Prisma Compute functionality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jun 17, 2026, 11:00 AM

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/blog/content/blog/prisma-compute-config-file/index.mdx`:
- Around line 1-14: The frontmatter for this blog post is missing the
heroImagePath and metaImagePath fields that are referenced in the PR objectives
as assets stored in apps/blog/public. Add these two optional fields to the
frontmatter block between the existing title, slug, date, and authors fields,
with paths pointing to the corresponding image assets for the
prisma-compute-config-file post (ensure the assets actually exist in the
apps/blog/public directory structure), or alternatively if these assets don't
exist yet, create them following the naming conventions used by other posts in
the series and then reference them in the frontmatter.

🪄 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: 3308ff85-b59e-4bdd-a470-405b49b4399b

📥 Commits

Reviewing files that changed from the base of the PR and between 9370d4e and 56f1605.

⛔ Files ignored due to path filters (1)

• apps/blog/public/create-prisma-deploy-prisma-compute/imgs/create-prisma-terminal.png is excluded by !**/*.png

📒 Files selected for processing (3)

• apps/blog/content/blog/create-prisma-deploy-prisma-compute/index.mdx
• apps/blog/content/blog/prisma-compute-config-file/index.mdx
• apps/blog/source.config.ts

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if hero/meta images exist for this post
ls -la apps/blog/public/prisma-compute-config-file/ 2>/dev/null || echo "No assets directory for this post"

# Search for other posts tagged with series: prisma-compute
rg -l "series:\s*prisma-compute" apps/blog/content/blog/ | sort

Repository: prisma/web

Length of output: 346

---

🏁 Script executed:

#!/bin/bash
# Extract frontmatter from all prisma-compute series posts to check seriesIndex values
for post in apps/blog/content/blog/bun-rust-rewrite-prisma-compute/index.mdx \
            apps/blog/content/blog/launching-prisma-compute-public-beta/index.mdx \
            apps/blog/content/blog/prisma-compute-config-file/index.mdx \
            apps/blog/content/blog/prisma-compute-custom-domains/index.mdx; do
  echo "=== $(basename $(dirname $post)) ==="
  head -20 "$post" | grep -E "^(title|seriesIndex|date|slug):"
done

# Also check if the first post slug referenced in the current post exists
rg -l "slug.*create-prisma-deploy-prisma-compute" apps/blog/content/blog/

Repository: prisma/web

Length of output: 803

---

Resolve the missing hero and meta image assets referenced in the PR objectives.

The PR objectives state that assets are stored in apps/blog/public for the configuration post, but no assets directory exists for this post (prisma-compute-config-file), and the frontmatter lacks heroImagePath and metaImagePath fields. While the schema allows these to be optional, the PR scope explicitly mentions these assets—so either add them or clarify why they're intentionally omitted from this post.

The seriesIndex: 4 is correct—this is chronologically the fourth post in the prisma-compute series.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/blog/content/blog/prisma-compute-config-file/index.mdx` around lines 1 -
14, The frontmatter for this blog post is missing the heroImagePath and
metaImagePath fields that are referenced in the PR objectives as assets stored
in apps/blog/public. Add these two optional fields to the frontmatter block
between the existing title, slug, date, and authors fields, with paths pointing
to the corresponding image assets for the prisma-compute-config-file post
(ensure the assets actually exist in the apps/blog/public directory structure),
or alternatively if these assets don't exist yet, create them following the
naming conventions used by other posts in the series and then reference them in
the frontmatter.