rayan/next-learn
1
0
Fork 0
mirror of https://github.com/vercel/next-learn.git synced 2026-06-12 10:21:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

Simplify language

Browse Source
This commit is contained in:
Shu Uesugi
2020-04-16 16:34:20 -07:00
parent 541204cd0f
commit 60f51ec929
5 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
api-routes-starter/posts/ssg-ssr.md
View File

@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.

2
basics-final/posts/ssg-ssr.md
View File

@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.

2
dynamic-routes-starter/posts/ssg-ssr.md
View File

@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.

2
typescript-final/posts/ssg-ssr.md
View File

@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.

2
typescript-starter/posts/ssg-ssr.md
View File

@@ -16,4 +16,4 @@ You should ask yourself: "Can I pre-render this page **ahead** of a user's reque
On the other hand, Static Generation is **not** a good idea if you cannot pre-render a page ahead of a user's request. Maybe your page shows frequently updated data, and the page content changes on every request.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and then use client-side JavaScript to populate data.
In that case, you can use **Server-Side Rendering**. It will be slower, but the pre-rendered page will always be up-to-date. Or you can skip pre-rendering and use client-side JavaScript to populate data.