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.
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
docs: Rewrite Rendering Section and React Essentials Page #51579
Conversation
Notifying the following users due to files changed in this PR: @timneutkens, @ijjk, @shuding, @huozhi, @feedthejim:
This comment was posted based on the notify modifier. |
All broken links are now fixed, thank you! |
This PR document the caching semantics in Next.js, how they interact, and what APIs affect them. We're also taking the opportunity to consolidate terminology, remove duplicate content, and update sections of the docs that relate to caching. ### Documentation - [x] Create a new section for caching - [x] Explain how the different caching mechanisms work - [x] Request Memoization (React Cache) - [x] Persistent Data Cache - [x] Persistent Full Route Cache - [x] In-memory, client-side Router Cache - [x] Document how different APIs affect caching - [x] Document cache interactions - [x] Clean up stale information in the other docs sections - [x] Routing Section - [x] Move advanced navigation topics from fundamentals to **How Navigation Works** section - [x] Rewrite the **How Navigation Works** section - [x] Rendering Section - [x] Simplify fundamentals page - [x] Rewrite the **Static and Dynamic Rendering** pages - [ ] ~Create a page to explain how **Client and Server Components** are rendered~. Moved to this PR: #51579 - [x] Data fetching section - [x] Consolidate data fetching story for fetching, caching, and revalidating - [x] Clarify data fetching story with 3rd party libraries and React `cache` - [x] Create **Data Fetching Patterns** page - [x] Document other related behaviors: - [x] Update information on scroll position for back/forward navigation - [x] Remove the concepts of **soft and hard navigation** - [x] Remove the concepts of **static and dynamic data fetching** - [x] Use consistent terminology **runtime** 👉🏼 **request time**. Runtime for Edge and Node.js, request time to describe when dynamic stuff happens - [x] `generateStaticParams` being able to seed the Full Route Cache - [x] Polish 💅🏼 --- ### Related PRs: - Diagrams: vercel/front#24142 - Redirects: vercel/front#24179
docs/02-app/01-building-your-application/03-rendering/03-composition-patterns.mdx
Outdated
Show resolved
Hide resolved
…cel/next.js into docs-react-essentials-revamp
Ok, these changes are ready for review 🎉 I'll work on diagrams separately. |
docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
Outdated
Show resolved
Hide resolved
…r-components.mdx Co-authored-by: Michael Novotny <manovotny@gmail.com>
docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/01-server-components.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/02-client-components.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/02-client-components.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/03-composition-patterns.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/03-composition-patterns.mdx
Outdated
Show resolved
Hide resolved
docs/02-app/01-building-your-application/03-rendering/index.mdx
Outdated
Show resolved
Hide resolved
I see there is still a
|
Co-authored-by: Michael Novotny <manovotny@gmail.com>
…sition-patterns.mdx Co-authored-by: Michael Novotny <manovotny@gmail.com>
This is going to be an absolute game changer when released. It totally reaches to the heart of the concepts and is going to unlock a lot of understanding. Amazing work @delbaoliveira, honestly can't wait. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Orca Security Scan Summary
Status | Check | Issues by priority | |
---|---|---|---|
Passed | Secrets | 0 0 0 0 | View in Orca |
Thank you @AndKenneth ❤️ |
Great work @delbaoliveira 👏 |
We initially wrote the React page to introduce Server Components in the App Router, but over time, some implementation details have changed, and the information has become stale. The React team is working on adding new docs, so I'd like to change the narrative on the Next.js docs from "client vs. server components" to "writing code for the server and for the client" - and link back to the React documentation when it becomes available.
As React developers, we're very familiar with writing code for the client, it's nice and simple. But doing so comes at the expense of not being familiar with the server. The aim of these docs is to help developers become proficient in both the client and server environments.
I'd like to take it back to the foundations, and not use abstractions like SSG and CSR, MPAs or SPAs, as those terms come with their own set of assumptions that make it harder to understand how RSC works. Instead, we'll focus on the request lifecycle, show how application code flows from the server to the client, and discuss the trade-offs of doing operations in each environment.
Diagramswill follow up with new PR.