[mirror] docs: add RSC migration success stories page (#1985)#3
Open
yashwant86 wants to merge 11 commits into
Open
[mirror] docs: add RSC migration success stories page (#1985)#3yashwant86 wants to merge 11 commits into
yashwant86 wants to merge 11 commits into
Conversation
Adds docs/pro/react-server-components/success-stories.md summarizing publicly reported results from teams that have shipped React Server Components to production (DoorDash LCP wins, Mux 50k-line migration, Frigade 62% bundle reduction, BlogHunch 30% server cost reduction, Nanobebe conversion lift, Developerway's honest analysis), with a comparison table, source links, and pointers to the corresponding React on Rails Pro docs. Cross-links the new page from the RSC index, the migration guide, and the Docusaurus sidebar so readers can find it from the places where they are most likely to be building the migration business case. Closes shakacode#1985 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Add DoorDash source link (DoorDash Engineering blog post on Next.js page performance) in the table, body, and References section so the 65%/67%/95% LCP figures are verifiable, matching the format of the other case studies. - Hide the AI-agent summary as an HTML comment so it does not render for human readers in the Docusaurus site.
- Add DoorDash careers site to lychee exclude list (Cloudflare 403s were blocking markdown-link-check CI) - Scope DoorDash to "Next.js SSR migration, pre-App Router" since the source article predates RSC and App Router - Note that Mux case study does not publish a specific % metric - Remove hidden AI-agent HTML comment (convention not used elsewhere; intro paragraph already describes the page) - Fix word repetition: "the benchmark to benchmark against"
The success-stories page explicitly notes DoorDash's write-up predates Next.js App Router / RSC. The index.md summary previously lumped DoorDash with teams that migrated to RSC, overstating the evidence for RSC-specific outcomes. Reword so DoorDash is framed as an earlier SSR migration that paved the way for RSC adoption. Addresses review feedback from @chatgpt-codex-connector[bot] on shakacode#3162. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Reword migrating-to-rsc.md intro so DoorDash is framed as an earlier Next.js SSR migration that paved the way for RSC, consistent with the qualification already made in index.md and the success-stories page - Surface Entesta as the vendor behind the BlogHunch case study in the Reported Results table so readers can judge first-party vs third-party sourcing at a glance
Restructures the Real-World Results teaser in index.md and the Why Migrate teaser in migrating-to-rsc.md so DoorDash's SSR numbers are presented in a separate sentence as an SSR baseline rather than being grouped with RSC-specific case studies. Also removes "paved the way for RSC adoption" phrasing since the DoorDash source article does not make that claim. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Fix DoorDash URL slug (throughserver → through-server) at all three occurrences; lychee excludes careersatdoordash.com so CI wouldn't have caught it - Add explicit pre-RSC qualifier to DoorDash baseline in page intro - Call out BlogHunch provenance in the section body (Entesta is the migration vendor, not a first-party engineering post) so readers skimming sections still see the attribution - Lead Mux row with the concrete Suspense-streaming mechanism instead of "no specific % published" so the row pulls its weight Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ins paragraph - Add "(SSR Baseline, pre-RSC)" qualifier to the DoorDash H2 in success-stories.md so skim-readers register the baseline framing without relying on the following paragraph - Replace the run-on "Teams adopting RSC report concrete wins..." paragraph in migrating-to-rsc.md with a scannable bulleted list, per claude[bot]'s inline suggested rewrite, and update the DoorDash anchor to match the new section heading Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Addresses two of three follow-ups from @claude[bot]'s 2026-04-23 review: - index.md:95 — replace vague "and others" with "Developerway's independent analysis" so the teaser accurately names the fifth entry (an analysis piece, not a team case study). - success-stories.md:17 — add a bold Note callout directly under the DoorDash heading warning readers not to cite the numbers as RSC results. Keeps the existing heading (and anchor) so the four deep links in migrating-to-rsc.md remain intact. Fragment-anchor verification (third follow-up) confirmed locally via github-slugger: the double-hyphen anchors in migrating-to-rsc.md:20-23 match Docusaurus's slug output exactly, so no code change needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Addresses two unresolved review comments on shakacode#3162: - migrating-to-rsc.md:18: the intro said "teams that have shipped RSC in production" but the DoorDash bullet is explicitly pre-RSC SSR. Reword to "server-first rendering (RSC in production, plus DoorDash's pre-RSC SSR baseline)" to match the framing already used on success-stories.md. - success-stories.md:13: Developerway's Headline Result cell had a description instead of a metric like the other rows. Replace with "N/A — methodology analysis (no headline metric)" for at-a-glance table consistency. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
⚡ Risk Assessment —
|
| Files | Summary |
|---|---|
RSC Success Stories Documentationdocs/pro/react-server-components/success-stories.mddocs/oss/migrating/migrating-to-rsc.mddocs/pro/react-server-components/index.mddocs/sidebars.ts |
Adds new RSC migration success stories page showcasing real-world adoption results and integrates it into documentation navigation and related guides. |
Dig Deeper With Commands
/review <file-path> <function-optional>/chat <file-path> "<question>"/roast <file-path>
Runs only when explicitly triggered.
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
2 participants
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.
Mirror of upstream shakacode#3162 for benchmark. Do not merge.
Summary by MergeMonkey