Skip to content

Commit c7099e3

Browse files
authored
Fix headings and add link (#7626)
1 parent 1a4183a commit c7099e3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Diff for: src/content/learn/build-a-react-app-from-scratch.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -69,13 +69,13 @@ If you'd you're starting from scratch with React Native you'll need to use [Metr
6969

7070
</Note>
7171

72-
### Step 2: Build Common Application Patterns {/*step-2-build-common-application-patterns*/}
72+
## Step 2: Build Common Application Patterns {/*step-2-build-common-application-patterns*/}
7373

7474
The build tools listed above start off with a client-only, single-page app (SPA), but don't include any further solutions for common functionality like routing, data fetching, or styling.
7575

7676
The React ecosystem includes many tools for these problems. We've listed a few that are widely used as a starting point, but feel free to choose other tools if those work better for you.
7777

78-
#### Routing {/*routing*/}
78+
### Routing {/*routing*/}
7979

8080
Routing determines what content or pages to display when a user visits a particular URL. You need to set up a router to map URLs to different parts of your app. You'll also need to handle nested routes, route parameters, and query parameters. Routers can be configured within your code, or defined based on your component folder and file structures.
8181

@@ -87,7 +87,7 @@ We suggest using:
8787
- [Tanstack Router](https://tanstack.com/router/latest)
8888

8989

90-
#### Data Fetching {/*data-fetching*/}
90+
### Data Fetching {/*data-fetching*/}
9191

9292
Fetching data from a server or other data source is a key part of most applications. Doing this properly requires handling loading states, error states, and caching the fetched data, which can be complex.
9393

@@ -128,7 +128,7 @@ Since the build tool you select only support single page apps (SPAs) you'll need
128128

129129
* **Streaming Server-side rendering (SSR)** renders a page on the server and sends the fully rendered page to the client. SSR can improve performance, but it can be more complex to set up and maintain than a single-page app. With the addition of streaming, SSR can be very complex to set up and maintain. See [Vite's SSR guide]( https://vite.dev/guide/ssr).
130130

131-
* **Static site generation (SSG)** generates static HTML files for your app at build time. SSG can improve performance, but it can be more complex to set up and maintain than server-side rendering.
131+
* **Static site generation (SSG)** generates static HTML files for your app at build time. SSG can improve performance, but it can be more complex to set up and maintain than server-side rendering. See [Vite's SSG guide](https://vite.dev/guide/ssr.html#pre-rendering-ssg).
132132

133133
* **React Server Components (RSC)** lets you mix build-time, server-only, and interactive components in a single React tree. RSC can improve performance, but it currently requires deep expertise to set up and maintain. See [Parcel's RSC examples](https://github.com/parcel-bundler/rsc-examples).
134134

0 commit comments

Comments
 (0)