copy(compute): align landing page copy with messaging skills + SEO#7929
Open
ankur-arch wants to merge 3 commits into
Open
copy(compute): align landing page copy with messaging skills + SEO#7929ankur-arch wants to merge 3 commits into
ankur-arch wants to merge 3 commits into
Conversation
Apply the Prisma communication skills (prisma-copy-review +
prisma-product-messaging) to the Compute landing page copy.
- Remove all em dashes from user-facing copy (page hero/meta, feature
bullets, comparison card benefits, How-it-works tabs).
- Cut fluff and vague intensifiers: "actually", "ultra-low latency",
"grows into jobs", and the "felt as good as the code" line, which is
reframed around the integrated-platform narrative from the
positioning doc (fewer separate build/hosting/database tools).
- Replace dramatic fragments ("Push code. It runs.", "Sockets stay
open. Streams flow uninterrupted.") with single workflow sentences,
and name the mechanism (long-lived process on Bun) in the hero/meta.
- Fix a broken cross-reference ("See the AI workloads section above" —
no such section exists).
- Mark capabilities not yet covered by the Compute docs as "Coming
soon": co-located database (feature card + bento + How-it-works tab)
and reliability automation (auto scaling/recovery/OOM).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThis PR updates marketing copy and SEO across the Compute landing page: template subtitles and benefit text, how-it-works tab punctuation, feature/card descriptions, FAQ entries, hero text, headings, and page metadata. ChangesCompute landing page copy & metadata
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 ↗︎
|
![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: 3
🤖 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/site/src/app/compute/how-it-works.tsx`:
- Line 1259: Update the title string so the punctuation around the parenthetical
is correct: in the object that defines the title property (the "title" key in
apps/site/src/app/compute/how-it-works.tsx), remove the period before "(Coming
soon)" and place punctuation appropriately—e.g., change "Database right next to
your code. (Coming soon)" to "Database right next to your code (Coming soon)".
Ensure only the title value is modified.
In `@apps/site/src/app/compute/page.tsx`:
- Around line 117-130: The "Works with any database, no lock-in" bullet in the
list conflicts with the co-location claim (co-location is specific to Prisma
Postgres); update the copy in the list (the <li> containing "Works with any
database, no lock-in") to clearly scope the capability to Prisma Postgres (e.g.,
mention "Prisma Postgres co-location" or remove the "any database" phrase) so
the bullets don't imply same-region automatic co-location for all databases;
keep the Badge and subhead as-is and ensure the revised text appears alongside
the other list items in the same <ul> block.
- Around line 171-176: The AI-agent card object titled "Building an AI agent?"
is incorrectly signaling availability via badgeColor: "ppg" while other
co-location items are marked "Coming soon"; update that card's availability to
match by changing its badge status (the badgeColor property on the "Building an
AI agent?" card) to the same "coming soon" token used for "Co-located
database"/"DB connected by default" or alternatively remove/soften the
"co-located memory" claim in the description so the badge and copy consistently
read "Coming soon".
🪄 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: 574f43ad-5df1-4a74-87aa-ec25befe12e2
📒 Files selected for processing (3)
apps/site/src/app/compute/components.tsxapps/site/src/app/compute/how-it-works.tsxapps/site/src/app/compute/page.tsx
Drop the "Coming soon" markers and tighten remaining empty language,
plus SEO fields.
- Remove "Coming soon" badges/label (co-located feature card, two
bento cards, How-it-works tab).
- Empty/slogan language replaced with concrete claims:
- "Compute keeps it all together." -> "One service for your app,
assets, and jobs." (matches the comparison cards below it)
- "No runtime constraints." -> "not a constrained edge runtime"
- SEO: page title and OG title now carry the primary keyword phrase
("Deploy TypeScript apps to production") instead of the bare brand
name; meta description tightened under ~155 chars; OG image alt made
descriptive.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ankur-arch
changed the title
The "Building an AI agent?" card carried a green YES badge while claiming "co-located memory", which reads as an availability promise for the database co-location story. Reword to "in-process memory", which describes the long-lived stateful runtime the page already presents as available, so the card no longer implies co-location availability. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Editorial and SEO pass on the Compute landing page copy, aligned with our internal product-messaging and copy-review guidelines. Targets
feat/DR-8328-compute-pageso it can be reviewed alongside the page.What changed
Voice and style
Push code. It runs.toPush code, it runs.plus a concrete clause; combined the WebSockets/streaming lines on the Hono card.Automatic scaling, automatic recovery, automatic handling of OOM conditionstoAutomatic scaling, recovery, and OOM handling).Clarity
Compute keeps it all together.toOne service for your app, assets, and jobs.No runtime constraints.tonot a constrained edge runtimeultra-low latencytolow-latency access;grows into jobstofor APIs and background jobs.SEO
Note for reviewers
A few product specifics on the page (pricing, performance characteristics, and stage of some capabilities) are worth a final confirmation from the Compute team before publish. I can adjust wording once those are confirmed.
🤖 Generated with Claude Code
Summary by CodeRabbit