Skip to content

docs(blog): add draft post on RSC as a protocol before an architecture#868

Merged
tannerlinsley merged 1 commit intomainfrom
taren/nifty-bohr-e19bb1
Apr 28, 2026
Merged

docs(blog): add draft post on RSC as a protocol before an architecture#868
tannerlinsley merged 1 commit intomainfrom
taren/nifty-bohr-e19bb1

Conversation

@tannerlinsley
Copy link
Copy Markdown
Member

@tannerlinsley tannerlinsley commented Apr 28, 2026

Summary

  • New draft blog post: "RSC Is a Protocol Before It Is an Architecture"
  • Adds two SVG figures (composition models, Flight cache pipeline) under public/blog-assets/rsc-is-a-protocol-before-it-is-an-architecture/
  • Marked draft: true so it does not appear on the public blog index

Test plan

  • Verify post is hidden from blog index (draft filter)
  • Preview draft locally and confirm both SVG figures render

Summary by CodeRabbit

  • Documentation
    • Added a new comprehensive blog article exploring React Server Components as a flexible network protocol. Covers multiple architectural approaches, composition patterns, transparent caching strategies, deeper integration with broader application pipelines, practical decision-making guidance, and best practices for implementing the most suitable approach for your specific requirements and use cases.

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 28, 2026

Deploy Preview for tanstack ready!

Name Link
🔨 Latest commit b84742e
🔍 Latest deploy log https://app.netlify.com/projects/tanstack/deploys/69f0dad43b75140008abaaac
😎 Deploy Preview https://deploy-preview-868--tanstack.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 29 (🔴 down 26 from production)
Accessibility: 90 (no change from production)
Best Practices: 83 (🔴 down 9 from production)
SEO: 97 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 28, 2026

📝 Walkthrough

Walkthrough

A new blog article is added introducing React Server Components (RSC) as a network serialization protocol rather than a fixed architecture. The post contrasts server-owned and client-owned composition models, discusses RSC as a primitive within a broader development pipeline, and provides guidance on caching strategies and model selection.

Changes

Cohort / File(s) Summary
Blog Article: RSC Protocol Overview
src/blog/rsc-is-a-protocol-before-it-is-an-architecture.md
New article (275 lines) presenting RSC as a serialization protocol, contrasting composition models (use client directive vs. client-owned Composite Components), explaining transparent caching in TanStack Start, and providing practical guidance on when to use each model.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A protocol speaks, not fixed in stone—
RSC trees of shared and own,
Server and client dance as one,
Through Flight and cache, the work is done!
Wisdom rendered, fresh and bright,
Makes React servers feel just right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding a draft blog post about RSC. It is specific, concise, and clearly indicates both the type of change (docs/blog) and the primary topic.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch taren/nifty-bohr-e19bb1

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
src/blog/rsc-is-a-protocol-before-it-is-an-architecture.md (1)

16-273: Run one editorial pass for compound-adjective hyphenation consistency.

There are many recurring phrases that should be hyphenated for readability and style consistency (e.g., Line 16 non-JSON, Line 16/52/95+ server-owned, Line 32/149+ client-owned, Line 24/62+ server-rendered, Line 52/233 SEO-driven, Line 217 client-side, Line 239 data-rich, Line 183 platform-owned, Line 189 deployment-specific).

✍️ Suggested pattern examples
- non JSON
+ non-JSON

- server owned tree
+ server-owned tree

- client owned model
+ client-owned model

- server rendered content
+ server-rendered content

- SEO driven pages
+ SEO-driven pages

- client side store
+ client-side store
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/blog/rsc-is-a-protocol-before-it-is-an-architecture.md` around lines 16 -
273, Run an editorial pass across the document to consistently hyphenate
compound adjectives: change instances like "non JSON" to "non-JSON", "server
owned" to "server-owned", "client owned" to "client-owned", "server rendered" to
"server-rendered", "SEO driven" to "SEO-driven", "client side" to "client-side",
"data rich" to "data-rich", "platform owned" to "platform-owned", and
"deployment specific" to "deployment-specific" (search for these exact
unhyphenated phrases from the diff and update them throughout the file to the
hyphenated forms for consistency).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/blog/rsc-is-a-protocol-before-it-is-an-architecture.md`:
- Around line 16-273: Run an editorial pass across the document to consistently
hyphenate compound adjectives: change instances like "non JSON" to "non-JSON",
"server owned" to "server-owned", "client owned" to "client-owned", "server
rendered" to "server-rendered", "SEO driven" to "SEO-driven", "client side" to
"client-side", "data rich" to "data-rich", "platform owned" to "platform-owned",
and "deployment specific" to "deployment-specific" (search for these exact
unhyphenated phrases from the diff and update them throughout the file to the
hyphenated forms for consistency).

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c22d35d4-063c-4023-a576-41b20f7f298f

📥 Commits

Reviewing files that changed from the base of the PR and between e117e0e and b84742e.

⛔ Files ignored due to path filters (2)
  • public/blog-assets/rsc-is-a-protocol-before-it-is-an-architecture/flight_cache_pipeline.svg is excluded by !**/*.svg
  • public/blog-assets/rsc-is-a-protocol-before-it-is-an-architecture/two_inversions_rsc.svg is excluded by !**/*.svg
📒 Files selected for processing (1)
  • src/blog/rsc-is-a-protocol-before-it-is-an-architecture.md

@tannerlinsley tannerlinsley merged commit 1009cb6 into main Apr 28, 2026
7 of 8 checks passed
@tannerlinsley tannerlinsley deleted the taren/nifty-bohr-e19bb1 branch April 28, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant