Docs: one recommended getting-started path for the Prisma stack, for humans and agents - #8106
Open
ankur-arch wants to merge 14 commits into
Open
Docs: one recommended getting-started path for the Prisma stack, for humans and agents#8106ankur-arch wants to merge 14 commits into
ankur-arch wants to merge 14 commits into
Conversation
…and agent flows The docs landing now leads with a single integrated journey (scaffold with Prisma Next, create or connect Prisma Postgres, deploy on Prisma Compute) instead of three parallel product commands. Prisma 7 stays one click away as the clearly labeled GA path. - /docs and /next: focused landing pages with quick setup, guided setup, copyable agent prompts, a framework logo grid, progressive-disclosure accordions for alternate paths, and a Browse-the-docs section. Sidebar is visually hidden on these two pages via a new hideSidebar frontmatter flag (pages stay in nav, search, sitemap, and llms.txt). - Agent prompts for every flow: new app, existing project, external Postgres, Prisma 7 full stack, and ORM-/Postgres-/Compute-only, all verified against npm dist-tags and live runs. - Framework guides (Next.js, Hono, TanStack Start, NestJS, Astro, Nuxt, SvelteKit, Elysia, Bun, Deno) validated end to end against live Prisma Postgres and extended with agent prompts plus Compute deploy legs where supported; 7 real deploys verified. Documented real traps: templates still emit the unqualified db.orm.User form, Next.js needs output standalone, TanStack needs nitro, Astro needs the node adapter and HOST=0.0.0.0. - New TechIcon MDX component and local framework logos (hono, nestjs, bun, tanstack copied from apps/site) with dark-mode handling. - orm/postgres/compute/orm-next index pages gain stack-continuation blocks and flow-specific prompts; getting-started nav reordered with Prisma Next first and Prisma 7 labeled; orphaned next/prisma-postgres pages wired into the sidebar. Validated: types:check, lint:links, lint:agent-ready, lint:images, lint:spellcheck all green; audit:redirects clean; desktop/mobile and light/dark screenshots checked; .md endpoints verified for agent parity. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…d-teamed agent prompts Compresses the getting-started landing from five scroll-screens to two using Supabase-style visual components while keeping every word crawlable and in the .md/llms agent output. - New components (src/components/getting-started.tsx): HeroGrid + StackSteps (numbered product steps with ORM/Postgres/Compute icons), GetStartedTabs (CLI / AI Prompt tab card with copy, Show more truncation), AgentPrompt (collapsed click-to-copy prompt rows with guide links), SectionRow (two-column Supabase-style sections), IconGrid/IconLink (compact logo links). Prompts are authored as fenced children, so SEO crawlers see the text and llm-markdown emits it; llm-markdown.ts gains converters for all new components (fidelity snapshots pass). - Landing rewritten around the components; /next gets the icon grid and a collapsed prompt; all product pages and the 10 framework guides swap raw prompt fences for AgentPrompt rows. Deno logo added; full:true on /. - All 20 agent prompts red-teamed by an adversarial agent role-playing a literal coding agent, and every finding applied: non-interactive Prisma 7 scaffold with --no-deploy, auth guards before browser-opening steps, template-aware deploy requirements (standalone/nitro/astro-adapter/ --framework bun, svelte excluded), contract:emit before migration plan, migrate --yes, stop-and-ask rules for unresolved placeholders and missing connection strings, driver-adapter step in the Prisma 7 ORM prompt, create-db claim-URL surfacing, curl-based verification, bounded log reads, and the Compute deploy page's agent notes moved inside the copyable block. Validated: types:check, lint:links, lint:agent-ready, lint:images, lint:spellcheck, test:llm-markdown all green; .md output of the landing verified clean of JSX residue; desktop/mobile/dark screenshots reviewed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…out polish Addresses review feedback on the redesigned landing: - Sidebar no longer flashes on load: page.tsx server-renders a scoped style that collapses the sidebar column and hides the desktop sidebar before hydration. Desktop-only, so the mobile drawer behind the hamburger keeps working (it was previously dead on hidden-sidebar pages). - New hero: left pitch with Recommended badge and two CTA buttons (quickstart, deploy), right StackDiagram visual showing Compute over Prisma Next over Prisma Postgres with connectors and a type-safe caption. Every layer links straight into its getting-started flow, so clicking "Prisma Postgres" lands on the quickstart, not a product overview. - The AI Prompt / CLI card is now full width below the hero, defaults to the AI Prompt tab, and its CLI tab carries the full command sequence (scaffold through deploy), replacing the removed "Run it, then ship it" section that duplicated commands and left dead space. - Consistency and readability pass: section left-column text enlarged, 4/8 column ratio, tighter AgentPrompt rows with ghost view toggle, consistent vertical rhythm, lucide connector icon. - llm-markdown converters updated (HeroPitch, StackDiagram/StackLayer, template-literal cli extraction, indent cleanup) so the .md output keeps the pitch, CTAs, product layers, CLI commands, and prompts; fidelity snapshots pass. - Verified nothing was removed from the old structure: git diff shows no deleted pages and the nav diff is reorder plus previously-orphaned next/prisma-postgres pages added. Validated: types:check, lint:links, lint:agent-ready, lint:spellcheck, test:llm-markdown green; SSR HTML contains the sidebar-hiding style; screenshots at 1440/1024/390 and dark mode reviewed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…mpt, CLI steps - New /next/full-stack-tutorial page: one validated walkthrough from empty directory to live URL (scaffold with Prisma Next, Prisma Postgres provisioning, seed and query, Prisma Compute deploy), built from the live-verified hono run with real output blocks. Wired into the getting started nav, the /next cards, and the hero's primary CTA. - Spacing pass: sections py-16 with wider gaps, roomier prompt rows and hero, capped left-column line length, larger grid gaps. - Prompt card: the whole AI Prompt area is now click-to-copy (keyboard accessible, "Click to copy"/"Copied" affordance, nested code-block buttons hidden); CLI tab renders labeled step groups instead of a flat command dump. - Recommended chip restyled as a quiet uppercase label; removed the awkward "also has the agent prompt" orphan line under the Prisma 7 cards (folded into the card description). Validated: types:check, lint:links, lint:spellcheck, lint:agent-ready, test:llm-markdown green; zero page errors in the browser console; click-to- copy verified end to end via Playwright clipboard read. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThe PR restructures Prisma onboarding around Prisma 7 and Prisma Next, adds agent-oriented setup prompts and reusable UI components, updates framework/runtime deployment guides, and extends MDX-to-markdown normalization for the new content. ChangesPrisma onboarding experience
Estimated code review effort: 4 (Complex) | ~60 minutes Sequence Diagram(s)sequenceDiagram
participant Developer
participant AgentPrompt
participant PrismaCLI
participant PrismaCompute
Developer->>AgentPrompt: Copy setup workflow
AgentPrompt->>PrismaCLI: Scaffold, initialize, seed, and deploy
PrismaCLI->>PrismaCompute: Deploy app with environment configuration
PrismaCompute-->>Developer: Return live URL for verification
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
… directive and details handler Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…Prisma 8 teasers - Hero AI prompt collapses behind a View prompt toggle; content stays in the DOM (sr-only) so crawlers and agents still see it, and wraps when expanded - Drop the db:seed failure admonition from the landing page (the prompt already carries the fix); give all docs admonitions roomier vertical rhythm - Icon tiles on the More setup paths rows; 5 min badge on the Prisma 7 quickstart card; backtick spans in section descriptions render as code - Assertive cross-linked copy for the Express and MongoDB pointers, with breathing room after the grids - Tease Prisma Next as soon Prisma 8 across hero, stack diagram, and Prisma 7 sections - llm-markdown: AgentPrompt attrs tolerate JSX icon props; IconLink badge surfaces in .md output Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
Design + content pass from review feedback:
🤖 Generated with Claude Code |
Contributor
🍈 Lychee Link Check Report377 links: ✅ All links are working!Full Statistics Table
|
|
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: 5
🤖 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/docs/content/docs/`(index)/next/index.mdx:
- Line 53: Update the deployment guidance in the numbered step to map template
names explicitly to the reviewed guide slugs: use nextjs.mdx for Next.js,
nestjs.mdx for Nest, and sveltekit.mdx for Svelte; skip svelte before
constructing or following the framework guide URL, while preserving the existing
framework-specific deployment requirements.
In `@apps/docs/content/docs/guides/next/frameworks/astro.mdx`:
- Line 41: Update the verification steps in
apps/docs/content/docs/guides/next/frameworks/astro.mdx#L41-L41,
apps/docs/content/docs/guides/next/frameworks/elysia.mdx#L31-L31, and
apps/docs/content/docs/guides/next/frameworks/hono.mdx#L31-L31 to start each dev
server in the background, wait until it is ready before running curl, and stop
the server after verification and subsequent deploy or cleanup steps.
In `@apps/docs/content/docs/guides/next/frameworks/tanstack-start.mdx`:
- Around line 87-93: Replace the prose inside the npm-tagged code fence in the
“Deploy to Prisma Compute” section with the runnable command npm install nitro,
and move the explanatory text into surrounding prose. Preserve the clarification
that the package is nitro rather than nitropack and that nitro() from nitro/vite
is enabled only for builds.
In `@apps/docs/src/lib/llm-markdown.ts`:
- Around line 590-597: Update the GetStartedTabs transformation to use the
existing component-tag parser used by replaceComponentBlocks instead of the
regex opening-tag match, so cli template literals containing “>” are parsed
intact. Preserve the existing getAttribute, trimComponentContent, and bash-block
generation behavior.
- Around line 572-619: Move the protectFencedCodeBlocks() call to run before the
component-tag replacement chain so fenced examples are excluded from
transformations such as AgentPrompt, GetStartedTabs, SectionRow, and HeroPitch.
Keep the existing restoration step after the replacement pipeline and
normalization complete.
🪄 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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: fa100b79-9d55-4e15-b6c5-e87dd77a166d
⛔ Files ignored due to path filters (6)
apps/docs/public/img/technologies/bun.svgis excluded by!**/*.svgapps/docs/public/img/technologies/deno.svgis excluded by!**/*.svgapps/docs/public/img/technologies/hono.svgis excluded by!**/*.svgapps/docs/public/img/technologies/nestjs.svgis excluded by!**/*.svgapps/docs/public/img/technologies/prisma-postgres.svgis excluded by!**/*.svgapps/docs/public/img/technologies/tanstack.svgis excluded by!**/*.svg
📒 Files selected for processing (27)
apps/docs/content/docs/(index)/getting-started.mdxapps/docs/content/docs/(index)/index.mdxapps/docs/content/docs/(index)/meta.jsonapps/docs/content/docs/(index)/next/full-stack-tutorial.mdxapps/docs/content/docs/(index)/next/getting-started.mdxapps/docs/content/docs/(index)/next/index.mdxapps/docs/content/docs/(index)/prisma-compute/deploy.mdxapps/docs/content/docs/compute/index.mdxapps/docs/content/docs/guides/next/frameworks/astro.mdxapps/docs/content/docs/guides/next/frameworks/elysia.mdxapps/docs/content/docs/guides/next/frameworks/hono.mdxapps/docs/content/docs/guides/next/frameworks/nestjs.mdxapps/docs/content/docs/guides/next/frameworks/nextjs.mdxapps/docs/content/docs/guides/next/frameworks/nuxt.mdxapps/docs/content/docs/guides/next/frameworks/sveltekit.mdxapps/docs/content/docs/guides/next/frameworks/tanstack-start.mdxapps/docs/content/docs/guides/next/runtimes/bun.mdxapps/docs/content/docs/guides/next/runtimes/deno.mdxapps/docs/content/docs/orm/index.mdxapps/docs/content/docs/orm/next/index.mdxapps/docs/content/docs/postgres/index.mdxapps/docs/cspell.jsonapps/docs/source.config.tsapps/docs/src/app/(docs)/(default)/[[...slug]]/page.tsxapps/docs/src/components/getting-started.tsxapps/docs/src/lib/llm-markdown.tsapps/docs/src/mdx-components.tsx
…ups, CodeRabbit fixes Landing page hierarchy per product feedback (too many competing paths): - Hero pitch now defines Prisma before naming versions, keeps one primary CTA (tutorial); secondary CTA becomes "Prisma 7 docs" so existing users exit early without a competing journey. Stack layers link to product overviews instead of three different setup flows. - One-line bridge above the tabs card ties it to the tutorial (same journey, condensed); CLI deploy step discloses the free-account sign-in. - Framework picker reframed as a step in the same journey; SvelteKit/Deno local-only caveat stated up front instead of inside the prompt only. - Prisma 7 section moved above alternates; five alternate-path prompt rows now sit behind a native <details> disclosure (content stays in static HTML and .md output, keyboard accessible). - /next drops the duplicate "What you can try" card block; /next/getting-started drops the duplicate Prisma Postgres section; /getting-started leads with the recommended quickstart and folds deploy into its own section. - Fill empty Prerequisites on the Prisma 7 Prisma Postgres quickstart. CodeRabbit findings: - Template-to-guide slug mapping in the deploy step of the hero prompt (next/nest/svelte no longer produce dead .md URLs). - Framework guide prompts run the dev server in the background, wait for readiness, and stop it after verification. - TanStack Start guide: garbled npm fence replaced with `npm install nitro`. - llm-markdown: fenced code is protected before all component transforms (prefix-aware restore replays dedent/blockquote shifts on fence lines), and GetStartedTabs parses via the brace-aware component parser so `>` inside the cli template literal cannot truncate the match. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
Golden-path pass (b232dac)Addresses the product feedback ("still a lot of different paths... make secondary options less prominent") plus all five open CodeRabbit threads. Fewer decisions before starting. The landing page previously exposed two "start" mechanisms, three stack-layer links into three different setup flows, five alternate-path rows, and a Prisma 7 section, all at equal weight. Now:
Adversarial persona review (P7 user, newcomer, "Prisma = ORM" dev, ship-fast hacker) produced 12 fixes, applied where they held up: action-labeled CTAs, version-ladder repetition trimmed (kept in hero/stack/P7 per earlier direction), SvelteKit/Deno no-Compute caveat surfaced in the framework section instead of only inside the prompt, free-account requirement disclosed on the deploy CLI step, disclosure summary names the ORM-only escape hatch, EA copy on /next reworded to drop the "not the real path yet" undertone, and the empty CodeRabbit: template→guide slug mapping in the deploy prompt; background dev server with readiness+teardown in all eight framework guide prompts; TanStack Validated: Known remainders: the primary agent prompt is still triplicated (landing, /next, /next/getting-started) pending an MDX include mechanism; the drift risk is documented. SvelteKit/Deno still have no Compute leg (stated on-page). 🤖 Generated with Claude Code |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
apps/docs/src/lib/llm-markdown.ts (1)
699-708: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winDedent/collapse regexes run after fences are already restored, exposing real code-fence content to corruption.
protectedCode.restore(unescaped)executes first (Line 702) and the subsequent.replace()calls (Lines 703-707) are chained onto its already-restored result — i.e., fenced code is no longer a protected placeholder when these blind, fence-unaware regexes run. Any fenced example containing an indented line starting with####/###,- [,- **[, orN. **[(plausible in docs that show markdown/JSX syntax samples, which this very pipeline processes), or containing 3+ consecutive blank lines, will have its leading whitespace stripped or blank lines collapsed — silently corrupting the code sample. Two of these four dedent rules (- **[,\d+. **[) are new in this PR, extending the exposure window.Move
.restore()to wrap the entire dedent/collapse chain so it executes last, after fences have safely done their job as opaque placeholders:🛠️ Proposed fix
- return protectedCode - .restore(unescaped) - .replace(/^[ \t]+(#{3,4} )/gm, "$1") - .replace(/^[ \t]+(- \[)/gm, "$1") - .replace(/^[ \t]+(- \*\*\[)/gm, "$1") - .replace(/^[ \t]+(\d+\. \*\*\[)/gm, "$1") - .replace(/\n{3,}/g, "\n\n") - .trim(); + return protectedCode + .restore( + unescaped + .replace(/^[ \t]+(#{3,4} )/gm, "$1") + .replace(/^[ \t]+(- \[)/gm, "$1") + .replace(/^[ \t]+(- \*\*\[)/gm, "$1") + .replace(/^[ \t]+(\d+\. \*\*\[)/gm, "$1") + .replace(/\n{3,}/g, "\n\n"), + ) + .trim();Since the fenced-code placeholder token never matches
#{3,4},- [,- **[, or\d+. **[, running dedent before restore is safe for genuine headings/lists and eliminates the corruption risk for fence content.🤖 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/docs/src/lib/llm-markdown.ts` around lines 699 - 708, Update the transformation chain around protectedCode.restore so all dedent and consecutive-blank-line replacements run on the still-protected placeholder content, then invoke protectedCode.restore last. Preserve the existing unescaped restoration and replacement patterns while ensuring fenced-code contents remain opaque until every regex has completed.
🤖 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/docs/content/docs/`(index)/getting-started.mdx:
- Around line 42-44: Persist deployment environment variables before the
follow-on deployment guidance: in
apps/docs/content/docs/(index)/getting-started.mdx at lines 42-44, add a project
environment setup step or link to the environment-variable documentation between
the initial deploy and the “keep deploying/connect GitHub” instruction; apply
the same change in apps/docs/content/docs/guides/next/frameworks/nestjs.mdx at
line 32. Ensure both guides explain that --env .env is only a one-off deploy
input.
---
Outside diff comments:
In `@apps/docs/src/lib/llm-markdown.ts`:
- Around line 699-708: Update the transformation chain around
protectedCode.restore so all dedent and consecutive-blank-line replacements run
on the still-protected placeholder content, then invoke protectedCode.restore
last. Preserve the existing unescaped restoration and replacement patterns while
ensuring fenced-code contents remain opaque until every regex has completed.
🪄 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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: b2108b9e-1c86-4208-8a72-262364dbc5fc
📒 Files selected for processing (14)
apps/docs/content/docs/(index)/getting-started.mdxapps/docs/content/docs/(index)/index.mdxapps/docs/content/docs/(index)/next/getting-started.mdxapps/docs/content/docs/(index)/next/index.mdxapps/docs/content/docs/(index)/prisma-orm/quickstart/prisma-postgres.mdxapps/docs/content/docs/guides/next/frameworks/astro.mdxapps/docs/content/docs/guides/next/frameworks/elysia.mdxapps/docs/content/docs/guides/next/frameworks/hono.mdxapps/docs/content/docs/guides/next/frameworks/nestjs.mdxapps/docs/content/docs/guides/next/frameworks/nextjs.mdxapps/docs/content/docs/guides/next/frameworks/nuxt.mdxapps/docs/content/docs/guides/next/frameworks/sveltekit.mdxapps/docs/content/docs/guides/next/frameworks/tanstack-start.mdxapps/docs/src/lib/llm-markdown.ts
🚧 Files skipped from review as they are similar to previous changes (10)
- apps/docs/content/docs/guides/next/frameworks/tanstack-start.mdx
- apps/docs/content/docs/(index)/next/getting-started.mdx
- apps/docs/content/docs/guides/next/frameworks/hono.mdx
- apps/docs/content/docs/guides/next/frameworks/sveltekit.mdx
- apps/docs/content/docs/guides/next/frameworks/elysia.mdx
- apps/docs/content/docs/(index)/index.mdx
- apps/docs/content/docs/(index)/next/index.mdx
- apps/docs/content/docs/guides/next/frameworks/nextjs.mdx
- apps/docs/content/docs/guides/next/frameworks/nuxt.mdx
- apps/docs/content/docs/guides/next/frameworks/astro.mdx
…e wrap for prompts - Replace every Font Awesome icon in the getting-started components with lucide equivalents: fa-sparkles is not in the loaded FA set, which left the default AgentPrompt tile and the hero badge with empty boxes. The badge, tab icons, copy/check, chevrons, and arrows now render from lucide-react like the rest of the page's icons. - orm/index: move the "Prisma 7 Connection Requirements" heading out of the callout body into the :::note[...] title, so the icon aligns with the title line and the h3 no longer leaks into the TOC. - AgentPrompt expanded body wraps like the hero prompt ([&_pre]:w-full + pre-wrap) instead of a 2000px-wide horizontal scroll on mobile. - Verified at 390px: no horizontal overflow with the disclosure open and prompts expanded; header rows wrap cleanly. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
Icon + admonition + mobile fixes (287bca4)
🤖 Generated with Claude Code |
- GetStartedTabs: both tab panels share a fixed height with internal scrolling, so AI Prompt <-> CLI switching no longer shifts the page; the prompt is always visible (no View prompt toggle) with the click-to-copy affordance kept, and the caption is a static footer - AgentPrompt: expanded body is bounded (max-h + scroll) so View expands by a fixed amount instead of the full prompt height - getting-started: note that --env .env is per-deployment and point to project env vars for persistence (CodeRabbit follow-up) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
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/docs/content/docs/`(index)/getting-started.mdx:
- Line 44: Update the deployment instructions around the project env add command
to explicitly pass the dotenv file with the supported --file .env option, or
instruct users to export DATABASE_URL before running it; do not imply that --env
.env applies to this command.
🪄 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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 9a86ce91-27c7-4f51-b475-aa23a0de5205
📒 Files selected for processing (2)
apps/docs/content/docs/(index)/getting-started.mdxapps/docs/src/components/getting-started.tsx
🚧 Files skipped from review as they are similar to previous changes (1)
- apps/docs/src/components/getting-started.tsx
project env add with a bare KEY reads the shell environment, not .env; --file .env imports the values the deploy step actually used. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ma/web into feat/getting-started-revamp
The hero prompt tab shows a clipped preview with a fade into a View full prompt button; the full text opens in a native <dialog> overlay, so reading a prompt never reflows the page. AgentPrompt rows reuse the same modal for View. Prompt content stays mounted for crawlers, and both hero tabs keep equal heights. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
@coderabbitai approve |
Contributor
✅ Action performedComments resolved and changes approved. |
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.
Outcome
The docs entry pages presented Prisma ORM, Postgres, and Compute as three equal, unrelated first commands, and the recommended path was buried mid-sidebar. New users now land on one integrated journey — scaffold with Prisma Next (becomes Prisma 8 at GA), store data in Prisma Postgres, deploy on Prisma Compute — with a visual hero, a quick path, a guided path, and a copyable agent prompt for every flow. Prisma 7 stays one click away, clearly labeled as the current GA release.
What changed
Landing experience (
/docs,/docs/next)hideSidebarfrontmatter flag, server-rendered so it never flashes in; the mobile drawer keeps working. Pages stay in nav, search, sitemap, and llms.txt — nothing was deleted anywhere on the branch (git diff main --diff-filter=Dis empty)./next/full-stack-tutorial): empty directory → live URL in one sitting, built from a live-validated run with real output blocks. It is the hero's primary CTA.Agent prompts, verified and red-teamed
.md/llms.txt output (newllm-markdownconverters, fidelity snapshots pass).contract:emitbeforemigration plan, driver-adapter step for Prisma 7, curl-based verification.Framework guides (Next.js, Hono, TanStack Start, NestJS, Astro, Nuxt, SvelteKit, Elysia, Bun, Deno)
db.orm.Userform (crashes on Postgres), Compute deploys need--env .env, Next.js template lacksoutput: "standalone"(silent 504s — the docs previously claimed otherwise), TanStack needs Nitro, Astro needs the node adapter +HOST=0.0.0.0, Elysia/Bun need--framework bun --entry, NestJS dev under tsx needs explicit@Inject().How it was validated
types:check,lint:links,lint:agent-ready(llms.txt budgets OK),lint:images,lint:spellcheck,test:llm-markdown,audit:redirectsall green;.mdendpoints verified free of JSX residue; click-to-copy verified via Playwright clipboard read; screenshots reviewed at 1440/1024/390 in light and dark.Trade-offs and remaining gaps
create-prisma@nextwould let the notes be deleted.docs-gs-validationproject (plus the temp scaffold databases) in Console.🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation
Bug Fixes