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.

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: Fix formatting issues in the rendering docs #54517

Merged
merged 2 commits into from
Aug 24, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/01-getting-started/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
---
title: Getting Started
description: Learn how to create full-stack web applications with Next.js.
---
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
---
title: Data Fetching Patterns
nav_title: Patterns
description: Learn about common data fetching patterns in React and Next.js.
---

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Original file line number Diff line number Diff line change
@@ -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.
---

Expand Down Expand Up @@ -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.

Expand Down Expand Up @@ -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.

Expand Down