No actionable comments were generated in the recent review. 🎉

Walkthrough

Added an unlisted Pro compatibility stub page at docs/pro/home-pro.md and marked its ID as excluded from sidebar generation; updated sidebar comments to record the legacy pro/home-pro → pro/react-on-rails-pro mapping.

Changes

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Simplify the docs sidebar and Pro landing pages #2909: Updates the Pro landing page and sidebar handling for pro/home-pro compatibility stubs — directly related.

Poem

🐰 A tiny stub hopped into view,
Pointing the path to pages true.
Quick links shining, old routes now steer,
Pro docs beckon — come hop near! ✨

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.}

Review: Simplify the docs sidebar and Pro landing pages

Scope note: The PR title and description mention sidebar reorganisation (removing redundant top-level sections, nesting RSC under Pro, release-note archive pages), but the actual diff is a single 14-line file: docs/pro/home-pro.md. The commit log shows merge conflicts against docs/pro/react-on-rails-pro.md and docs/sidebars.ts were resolved during the latest merge commit — those changes appear to have been dropped in favour of main. Worth clarifying whether the sidebar simplification is intentionally deferred or was accidentally lost.

The compatibility page itself

All six relative links in the file resolve to existing files:

• ./react-on-rails-pro.md ✓
• ./installation.md ✓
• ./upgrading-to-pro.md ✓
• ./react-server-components/index.md ✓
• ./streaming-ssr.md ✓
• ./node-renderer.md ✓

The file is intentionally absent from docs/sidebars.ts, which is the right call for a backwards-compat route.

One actionable issue

See inline comment: Docusaurus v3 warns about docs that exist on disk but appear in no sidebar. Adding unlisted: true to the frontmatter silences that warning while still generating the URL — which is exactly the intent of this page. Since no full Docusaurus build was run locally, this would only surface in CI.

Greptile Summary

This PR simplifies the docs sidebar by regrouping content under cleaner top-level categories, moves RSC under "React on Rails Pro", surfaces "Deployment" as its own section, and adds a "Upgrading & Migration" section that aggregates both OSS and Pro upgrade docs. It also introduces docs/pro/home-pro.md as a unlisted: true compatibility stub keeping the old URL alive while pointing readers to the canonical Pro landing page.

All sidebar doc IDs I could verify resolve to real files on disk (upgrading/release-notes/index, pro/release-notes/index, building-features/node-renderer/*, migrating/*, pro/react-server-components/*), and the prior frontmatter concern (missing unlisted/description) was addressed in the final commit.

Confidence Score: 5/5

Safe to merge — documentation-only change with no runtime code impact.

All P2-or-lower findings; previous frontmatter concern was resolved in a7a20bc; verified sidebar doc IDs map to real files; no broken links or logic issues identified.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Old /pro/home-pro URL"] -->|"unlisted: true stub"| B["docs/pro/home-pro.md"]
    B -->|"redirect link"| C["docs/pro/react-on-rails-pro.md\n(canonical Pro landing)"]

    D["Sidebar docsSidebar"] --> E["Getting Started"]
    D --> F["Core Concepts"]
    D --> G["Building Features"]
    D --> H["Reference"]
    D --> I["Deployment"]
    D --> J["Upgrading & Migration"]
    D --> K["React on Rails Pro"]

    J --> L["upgrading/release-notes/index\n(OSS archive)"]
    J --> M["pro/release-notes/index\n(Pro archive)"]

    K --> N["pro/react-server-components/*\n(RSC — moved under Pro)"]
    G --> O["building-features/node-renderer/*\n(Node Renderer Pro — detailed articles)"]

_{Reviews (2): Last reviewed commit: "Add unlisted frontmatter to home-pro com..." | Re-trigger Greptile}

Re the scope question from @claude[bot]: the sidebar reorganization in sidebars.ts and react-on-rails-pro.md changes are present — they came in via the merge commit from main. The PR diff showing only home-pro.md is because gh pr diff compares the branch tip against the merge base, and those files were already on main. The changes are intentional and intact.

Re the P2 suggestion from @greptile-apps[bot] about noting pro/home-pro in the sidebars.ts excluded-files comment: addressed in a7a20bc.

Code Review

Overview

This PR adds a URL-compatibility stub (docs/pro/home-pro.md) for old links that pointed to /pro/home-pro, and documents the exclusion in docs/sidebars.ts. The change is documentation-only (20 lines added, nothing deleted) and carries no runtime risk.

What works well

• Correct Docusaurus pattern: Using unlisted: true in frontmatter is the right approach for a URL-compatibility page — the route remains accessible but is excluded from the sidebar and Algolia search index.
• All linked targets exist: Every relative link in the stub (./react-on-rails-pro.md, ./installation.md, ./upgrading-to-pro.md, ./react-server-components/index.md, ./streaming-ssr.md, ./node-renderer.md) resolves to a real file in the repo.
• No sidebar pollution: The stub is correctly absent from the sidebar tree in sidebars.ts.

Issues

Minor — comment block miscategorises pro/home-pro

See the inline comment on docs/sidebars.ts line 7. The home-pro entry is placed under the heading "legacy stubs that redirect to archive", but it redirects to a live, current page. A future editor could reasonably misread this and treat it as an archive link. The fix is a one-line comment change.

Observations (no action required)

• No true HTTP redirect: The stub serves content with links rather than issuing a 301/302. That is fine here because unlisted: true prevents search-engine indexing of the duplicate, and the page content is clear about where canonical content lives. A Docusaurus client-redirect plugin entry would give a cleaner UX, but is out of scope for this PR.
• No custom_edit_url: null: Unlisted pages sometimes set this to suppress the "Edit this page" footer button. Not strictly necessary, but worth noting if it becomes a pattern.

Summary

Safe to merge after the minor comment-block fix. All linked files exist, the Docusaurus unlisted pattern is used correctly, and the sidebar is untouched.

Code Review

Summary: Documentation-only PR that adds a URL-compatibility stub (docs/pro/home-pro.md) to preserve old links while redirecting users to the canonical Pro landing page. Changes also update .sidebar-exclusions and a comment in sidebars.ts to suppress the stub from navigation.

What Works Well

• All six linked files in the Quick Links section exist and are valid (verified locally): react-on-rails-pro.md, installation.md, upgrading-to-pro.md, react-server-components/index.md, streaming-ssr.md, node-renderer.md.
• unlisted: true frontmatter is the correct Docusaurus mechanism for hiding a page from nav/search while keeping its URL live.
• The .sidebar-exclusions entry is properly formatted with a reason comment, consistent with existing entries.

Minor Issues

Comment placement inconsistency in sidebars.ts

The new comment line is placed under the block header "Intentionally excluded from sidebar (legacy stubs that redirect to archive)", but home-pro is not a redirect to the archive plugin — it is a compatibility stub pointing to a peer page. The content is accurate but the grouping is slightly misleading. Consider moving the entry to its own block with a heading like // URL-compatibility stubs (live pages, not archive redirects):.

No full Docusaurus build validated

The PR description notes: "I did not run a full Docusaurus build in this workspace." While all referenced doc IDs exist on disk, a full build would catch any broken docId resolution or routing issues. Low-risk for a stub page, but worth noting if CI does not gate on a Docusaurus build.

Assessment

Low risk, clean change. The stub pattern is appropriate for URL compatibility, and the exclusion from sidebar/search is correctly implemented. The comment grouping fix in sidebars.ts is a minor suggestion and does not block merging.

Thanks @claude[bot]. The inline-comment categorization issue (the only actionable item flagged) is addressed in d7ed940 — pro/home-pro is now under a new "URL-compatibility stubs (redirect to a current, live page)" header, separate from the archive-redirect block. The scope question was answered above — the sidebar reorganization came in via the merge from main.

Review Round Summary

Addressed:

• docs/sidebars.ts comment block split — pro/home-pro now under a new "URL-compatibility stubs (redirect to a current, live page)" header, no longer mis-grouped with archive-redirect stubs (d7ed940). Thread resolved.

CI fixes (pushed alongside):

• Merged origin/main to pick up the docs/.sidebar-exclusions infrastructure from feat: add CI guard requiring sidebar updates when adding docs #3089.
• Added pro/home-pro to docs/.sidebar-exclusions so the new sidebar-check CI guard recognizes the intentional omission (c983afc). Verified locally: script/check-docs-sidebar passes.
• The earlier markdown-link-check failure was a transient "Connection failed" against https://tanstack.com/query/latest/docs/framework/react/guides/ssr in docs/oss/migrating/rsc-data-fetching.md — a file this PR does not modify. URL responds 200 OK locally; expecting the re-run to pass.

No further action needed on the bot review summaries (greptile 5/5, coderabbit "no actionable comments") — the only actionable inline issue from those summaries was the categorization fix above.

I (Claude Code) made these changes.

Code Review

Summary: Clean, low-risk docs-only change. Adds a URL-compatibility stub for pro/home-pro using Docusaurus's unlisted: true front matter — the right pattern for keeping legacy URLs live without cluttering the sidebar.

What's Good

• All 6 link targets in the stub (react-on-rails-pro.md, installation.md, upgrading-to-pro.md, react-server-components/index.md, streaming-ssr.md, node-renderer.md) exist and are valid.
• The exclusion entry in .sidebar-exclusions follows the established format and includes an explanatory comment consistent with existing entries.
• The comment block added to sidebars.ts fits the existing exclusion-comment pattern perfectly.

Minor Observations

1. No full Docusaurus build was run. The PR notes this explicitly. The stub's relative links (./react-on-rails-pro.md, etc.) are correct on the filesystem, but Docusaurus resolves Markdown links differently in some edge cases (e.g. index.md vs the directory slug). A pnpm build or pnpm start in the docs/ workspace would give full confidence before merge.

2. unlisted: true is a soft landing, not an HTTP redirect. Crawlers and bookmarks that hit pro/home-pro will receive a real page (200) with a manual link, not a 301. That's intentional per the PR description, but if SEO link-equity transfer matters, the @docusaurus/plugin-client-redirects plugin provides a true redirect. Given this is a compatibility stub for an internal docs re-org rather than an externally indexed page, the current approach is fine.

3. description front matter on unlisted: true pages is less useful since the page won't appear in search results or OpenGraph previews. It doesn't hurt, but it's minor noise.

Verdict

Approve after confirming either (a) a local Docusaurus build passes, or (b) CI runs the build successfully. The logical structure and file hygiene are solid.