Docs: Fix formatting issues in the rendering docs (#54517)
This commit is contained in:
parent
9bcd570bc1
commit
94b7743cbe
4 changed files with 9 additions and 6 deletions
4
docs/01-getting-started/index.mdx
Normal file
4
docs/01-getting-started/index.mdx
Normal file
|
@ -0,0 +1,4 @@
|
|||
---
|
||||
title: Getting Started
|
||||
description: Learn how to create full-stack web applications with Next.js.
|
||||
---
|
|
@ -1,6 +1,5 @@
|
|||
---
|
||||
title: Data Fetching Patterns
|
||||
nav_title: Patterns
|
||||
description: Learn about common data fetching patterns in React and Next.js.
|
||||
---
|
||||
|
||||
|
|
|
@ -90,7 +90,7 @@ Then, on the client:
|
|||
3. The JavaScript instructions are used to [hydrate](https://react.dev/reference/react-dom/client/hydrateRoot) Client Components and make their UI interactive.
|
||||
|
||||
> **What is hydration?**
|
||||
|
||||
>
|
||||
> Hydration is process of attaching event listeners to the DOM, to make the static HTML interactive. Behind the scenes, hydration is done with the [`hydrateRoot`](https://react.dev/reference/react-dom/client/hydrateRoot) React API.
|
||||
|
||||
### Subsequent Navigations
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Server and Client Composition Patterns
|
||||
nav_title: Patterns
|
||||
nav_title: Composition Patterns
|
||||
description: Recommended patterns for using Server and Client Components.
|
||||
---
|
||||
|
||||
|
@ -346,9 +346,9 @@ You can optimize your package by using ['use client' deeper in the tree](#moving
|
|||
|
||||
It's worth noting some bundlers might strip out `"use client"` directives. You can find an example of how to configure esbuild to include the `"use client"` directive in the [React Wrap Balancer](https://github.com/shuding/react-wrap-balancer/blob/main/tsup.config.ts#L10-L13) and [Vercel Analytics](https://github.com/vercel/analytics/blob/main/packages/web/tsup.config.js#L26-L30) repositories.
|
||||
|
||||
### Client Components
|
||||
## Client Components
|
||||
|
||||
#### Moving Client Components Down the Tree
|
||||
### Moving Client Components Down the Tree
|
||||
|
||||
To reduce the Client JavaScript bundle size, we recommend moving Client Components down your component tree.
|
||||
|
||||
|
@ -463,7 +463,7 @@ export default function ClientComponent({ children }) {
|
|||
}
|
||||
```
|
||||
|
||||
#### Supported Pattern: Passing Server Components to Client Components as Props
|
||||
### Supported Pattern: Passing Server Components to Client Components as Props
|
||||
|
||||
The following pattern is supported. You can pass Server Components as a prop to a Client Component.
|
||||
|
||||
|
|
Loading…
Reference in a new issue