Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[docs] Fixed 404 links to Layouts RFC blog post #39937

Merged
merged 1 commit into from Aug 25, 2022
Merged

[docs] Fixed 404 links to Layouts RFC blog post #39937

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/advanced-features/react-18/server-components.md
View file
Open in desktop
Expand Up @@ -4,15 +4,15 @@ Server Components allow us to render React components on the server. This is fun

### Next Router and Layouts RFC

We are currently implementing the [Next.js Router and Layouts RFC](/blog/layouts-rfc).
We are currently implementing the [Next.js Router and Layouts RFC](https://nextjs.org/blog/layouts-rfc).

The new Next.js router will be built on top of React 18 features, including React Server Components.

One of the biggest proposed changes is that, by default, files inside a new `app` directory will be rendered on the server as React Server Components.

This will allow you to automatically adopt React Server Components when migrating from `pages` to `app`.

You can find more information on the [RFC](/blog/layouts-rfc) and we welcome your feedback on [Github Discussions](https://github.com/vercel/next.js/discussions/37136).
You can find more information on the [RFC](https://nextjs.org/blog/layouts-rfc) and we welcome your feedback on [Github Discussions](https://github.com/vercel/next.js/discussions/37136).

### Server Components Conventions

Expand Down