React Server Components
React Bricks supports React Server Components in Next.js, so you can keep a modern server-first architecture without giving up visual editing.
React Server Components in React Bricks
What it is: React Server Components render non-interactive UI on the server, reducing the amount of JavaScript sent to the browser.
How React Bricks handles it: React Bricks supports React Server Components in Next.js, so content-driven pages can stay server-first while editors still work visually.
Why it matters: Developers can keep a modern performance-oriented architecture without losing the editorial benefits of visual content management.
What React Server Components change
Server Components run only on the server, which means non-interactive UI can be rendered without sending unnecessary JavaScript to the browser. Interactive pieces stay as client components and hydrate only where needed.
This model fits especially well for content-driven websites, where most of the page can stay server-rendered while only selected parts need interactivity.
How React Bricks fits with RSC
React Bricks works naturally with this approach. You can keep your content-driven pages server-first, render bricks through the App Router, and still let editors manage content visually inside the CMS. This is part of the broader Next.js CMS architecture.
React Bricks supports React Server Components with a straightforward integration that usually requires only minimal changes to brick code.
For a deeper understanding of how Server Components work and their benefits, read this article written by our CTO.
Read more about React Server Components support in our Documentation.