You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Walkthrough

Added a canonical Pro landing page and route-map callouts; replaced mixed OSS/Pro links in top-level docs with a single Pro route map entry; added route-map callouts on Pro feature pages and a new Fragment Caching Pro doc. Documentation-only changes; no code or public API modifications.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through pages, tidy and bright,
One map to Pro to guide the night.
Links aligned, fragments found their place,
A nimble trail for every case. ✨

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 @coderabbitai help to get the list of available commands and usage tips.}

Greptile Summary

This is a documentation-only PR that establishes docs/pro/home-pro.md as the canonical Pro landing page and routes all entry points (the main docs README and the OSS quick-start guide) through it before reaching feature-specific pages. Each Pro feature page (streaming-ssr.md, node-renderer.md, fragment-caching.md) also gains a back-link callout so readers who land on a deep page know where the route map lives.\n\nKey changes:\n- docs/pro/home-pro.md: New introductory paragraph and a Route Map table listing five "Need → Start here → Then read" paths\n- docs/README.md: Pro features section now leads with a pointer to home-pro.md; Streaming SSR and Node Renderer links updated from OSS build-feature pages to their Pro overview counterparts; Fragment Caching and Upgrading to Pro entries added\n- docs/oss/getting-started/quick-start.md: Pro upgrade tip and bullet list both now route through home-pro.md first\n- docs/pro/{fragment-caching,node-renderer,streaming-ssr}.md: Consistent route-map callout added at the top of each page\n\nOne issue found: the "Compare OSS and Pro" row in the Route Map table has its Start here and Then read columns reversed — a reader evaluating whether to upgrade should start with the comparison page, not the upgrade guide.

Confidence Score: 4/5

Safe to merge after fixing the inverted "Compare OSS and Pro" row in the route map table.

All six changed files are documentation only, all links resolve to existing files, and the structural intent is clear and correct. The single concrete issue — the "Start here"/"Then read" columns being reversed for the comparison row — is a one-line fix and would mislead readers who land on the route map looking to evaluate Pro.

docs/pro/home-pro.md — route map table row 1 needs the Start here / Then read columns swapped

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[docs/README.md\nPro features section] -->|Start at| B[docs/pro/home-pro.md\nCanonical Route Map]
    C[docs/oss/getting-started/quick-start.md\nGo Pro section] -->|Start at| B

    B -->|Compare OSS & Pro| D[upgrading-to-pro.md]
    B -->|Node.js SSR| E[node-renderer.md]
    B -->|Progressive SSR| F[streaming-ssr.md]
    B -->|Cache output| G[fragment-caching.md]
    B -->|RSC| H[react-server-components/tutorial.md]

    E -.->|Route map callout back| B
    F -.->|Route map callout back| B
    G -.->|Route map callout back| B

_{Reviews (1): Last reviewed commit: "docs: make Pro route entry points explic..." | Re-trigger Greptile}

Review: docs/pro navigation refactor

Overall this is a clean, well-structured improvement. All linked files exist and the navigation intent is clear. Two issues worth addressing:

1. Route map columns swapped for "Compare OSS and Pro" row (inline comment on home-pro.md:11)

The "Start here" entry for the comparison row points to upgrading-to-pro.md, which is the how-to-migrate guide. A reader who wants to compare features before deciding should start at oss-vs-pro.md. The columns are logically reversed for this row.

2. Streaming SSR route map callout links to RSC tutorial (inline comment on streaming-ssr.md:5)

Streaming SSR and RSC are independent features — you can use streaming SSR without RSC. Suggesting the RSC tutorial as a related path may send readers down the wrong fork. The streaming-server-rendering.md technical guide is a better "then read" target here.

Minor observation

The old docs/README.md Pro section included a direct link to Add RSC to Existing Pro App which has been removed. It's now only reachable via the route map table in home-pro.md. That's fine since home-pro.md is now the canonical entry point, but worth confirming this was intentional.

Review: docs: make Pro route entry points explicit

Good overall direction — having a canonical Pro landing page with a route map is a clear improvement over the previous scattered links. All file paths resolve correctly and the prose is clean. A few things worth addressing before merge:

Must-fix

• The 'Compare OSS and Pro' row in the home-pro.md route map has the columns swapped (see inline comment). Someone deciding whether to upgrade should start at the comparison page, not the upgrade guide.
• fragment-caching.md mentions 'Pro configuration docs' as plain text but omits the hyperlink (see inline comment).

Worth considering

• quick-start.md ends up with two links to home-pro.md within four lines — once in the tip block and once as a standalone bullet. The bullet is redundant.
• The upgrading-existing-pro-app.md link was dropped from docs/README.md with no alternative route for users who are already on Pro and want to add RSC. The route map in home-pro.md only covers the RSC tutorial, not the dedicated existing-Pro upgrade path. Either restore the link or add a row to the route map for that case.

Review: docs: make Pro route entry points explicit

Clean, well-scoped change. All file paths resolve correctly and the structural intent is clear. Two small fixes before merge:

Must-fix

• fragment-caching.md:5 — The route map callout mentions "SSR caching guide" and "Pro configuration docs" as plain text with no hyperlinks. Both references exist in the repo and should be linked (see inline comment with suggestion).
• quick-start.md:196 — A standalone bullet linking to home-pro.md appears two lines after the tip block that already links there. The bullet is redundant and can be removed (see inline comment).

Clarification on previous bot feedback
Several prior review comments (greptile, earlier claude reviews) flagged the "Compare OSS and Pro" row in the route map as having its columns swapped. Looking at the actual file, the order is correct: Start here → OSS vs Pro comparison, Then read → Upgrade to Pro. That is the right progression for someone evaluating a Pro purchase. Those comments can be dismissed.

Intentional change confirmed?
The direct link to Add RSC to Existing Pro App was removed from docs/README.md. That path is still reachable via the route map's RSC row (home-pro.md → "Then read" → upgrading-existing-pro-app.md), so this appears intentional and is fine.

Overall, this is a well-structured documentation improvement. All internal links are valid, the route map table is a genuinely useful navigation aid, and Fragment Caching is correctly elevated to a first-class entry in the main README.

A few items worth addressing:

1. Blockquote style vs. Docusaurus admonitions

The three route-map callouts in node-renderer.md, streaming-ssr.md, and fragment-caching.md use plain blockquote syntax (> **Route map**:), while the rest of the docs use Docusaurus named admonitions (:::note, :::tip, etc.). Plain blockquotes render as unstyled gray boxes in Docusaurus. Consider switching to a consistent admonition style, e.g. :::note Route map.

2. RSC page is missing the route-map callout

Three of the four Pro feature entry-point pages get the new callout, but docs/pro/react-server-components/tutorial.md does not. If the callout pattern is intentional for reader orientation, it should be applied to the RSC tutorial too.

3. Quick-start tip loses the key performance claim

The previous tip included "10-100x faster SSR" as a quantified selling point. The replacement drops that claim. Consider preserving it alongside the route-map pointer.

4. Route map "Then read" for RSC points to a migration guide

The RSC row links to upgrading-existing-pro-app.md as the follow-on read, which is a migration guide for existing Pro users. A feature overview or architecture doc would be a more natural next step for first-time RSC explorers.